Hi all Here is another update on TPP on Mac OS X. I just compiled and installed TPP-4.8.0 PHILAE on my system (Mac OS X 10.8.5). Everything runs smoothly, if both clang g++ and c++ are replaced by gcc-4.6 (http://sourceforge.net/p/proteowizard/mailman/message/31567983/). It seems that the PepXMLViewer.cgi problem is also solved. Thanks!
The only very minor problem is a path issue related to the 'Additional Analysis Info' button in PepXMLViewer. The new -MODELS.html file is generated, but the link set by '__modelsFileNameWeb__' (line 2313) is generated relative to cgiBase, where PepXMLViewer.cgi runs from. Thus, it reads e.g. '/tpp/cgi-bin/tpp/tpp_data/...' instead of '/tpp/tpp_data/...'. I guess this has to be adjusted in 'PipelineAnalysis.cxx'. It's very minor, since the -MODELS.html file is easily accessible from filebrowser. Or do I have to change some settings on my system? Thanks for keeping up the great work!! Cheers Ulrich On May 20, 2014, at 8:57 AM, Ulrich auf dem Keller <[email protected]> wrote: > Hi Luis > > To me it also seems like a Mac OS X specific bug. I'll also test the new > 4.7.1 in the near future and let you know if it is still a problem. For now, > I switched back to 4.6.3. > > Thanks a lot. > > Cheers > > Ulrich > > On May 14, 2014, at 10:04 PM, Luis Mendoza <[email protected]> > wrote: > >> Hi Ulrich, >> Is this still an issue on your system? I could not get it reproduced on >> Windows or Linux, so perhaps an OS X only bug? Or something with your >> specific file? Do you have access to a Windows or Linux installation to see >> if you can reproduce it? >> Cheers, >> --Luis >> >> >> >> On Fri, Mar 14, 2014 at 7:41 AM, Ulrich auf dem Keller <[email protected]> >> wrote: >> Hi >> >> While running TPP-4.7 compiled on Mac OS X 10.8.5 I found a memory leakage >> in the new PepXMLViewer.cgi. When using the 'Pick columns' tab to remove a >> column and then trying to add back this column later, the page does not >> refresh anymore and the PepXMLViewer.cgi process starts to fill up system >> memory, leading to kernel:memorystatus_threads in the system.log. >> >> Maybe, this is just specific to how Mac OS X manages RAM? >> >> Thanks for any help. >> >> Ulrich >> >> -- >> You received this message because you are subscribed to the Google Groups >> "spctools-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/spctools-discuss. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "spctools-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/spctools-discuss. >> For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "spctools-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/spctools-discuss. For more options, visit https://groups.google.com/d/optout.
