I haven't tried it in a long time, but if you call ProteinProphet manually, you can add the flags: EXCELPEPS EXCEL0. That excel file used to be a little different than the one generated by the web pages, but that might do it for you.
Greg On Thu, Jun 18, 2009 at 8:42 PM, Luis Mendoza <[email protected]>wrote: > Hello Dave, > There is a way you can do this on the command-line. Open a command window, > and type the following: > protxml2html.pl -file <FULL_PATH_TO_PROTXML_FILE> EXCEL > where the FULL_PATH... includes the drive designation (i.e. C:\ etc in > Windows). > This will produce a file of the same base name as the protxml, but with the > .xls suffix. > > Do note that this process also calls xslt, since we are transforming an xml > domcument. > > Hope this works for you, > --Luis > > > > On Thu, Jun 18, 2009 at 11:29 AM, Dave @ UPENN <[email protected]>wrote: > >> >> Ok, so I'm running into the problem where the web interface cannot >> seem to open interact.prot.xml because the file is just too large for >> the xslt translation. ProteinProphet used to have a feature where it >> would output excel right from the analysis. is there any way to >> currently do this? also, are there any recommendations how to get >> around this xslt size issue? I am running some pretty hefty servers, >> and i've also tried to use a saxon parser with no avail. >> >> thanks, >> dave >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "spctools-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/spctools-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
