The software is working just fine! Thanks for this. I have specified some peak IDs and the summary page looks exactly like I want it to be. Is there a way of easily extracting these information to a txt file or similar? The outputs I found are either in xlm or the single txt files for every sample (in the merged one, there are a lot of other information, so it is possible to read this, but seems unnecessarily cumbersome to extract it from there).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
Thanks for taking the time to comment. It is really nice to read what you have to say.
The results you want are already there, but make sure that in the Options setting of your method (the last tab) you have enabled all the outputs. That is the default setting so they should be on already.
Below the SpecProcResults folder there are 2 sets of data (but unless you go looking for it you would only see one of them through the web page view). In addition the most recent processed results are copied into the raw folder. The \SpecProcResuts\ path contains both xml, txt and all previous processing. The Raw folder only has the text version of the most recent.
If your project was called xyz then you would have
...\SpecProcResults\xyz_Files\
and
...\SpecProcResults\xyz_Merged\
Somewhere below these paths are the files you are after. When you have a lot of processing results in there it is a bit of a mind melter to navigate to the one you are actually after.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I should have added that the text files look overwhelming in Notepad, but they are set up so they drop straight into Excel. The column layout is predictable so once you know what columns to hide it becomes easily repetitious. The files (both text and xml) contain a lot of information as behind the scenes there is a lot of information (!) and it isn't possible to predict which bits are important to any particular user. So the approach was to stick it all in a file and let you (the user) get what you want with excel.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The software is working just fine! Thanks for this. I have specified some peak IDs and the summary page looks exactly like I want it to be. Is there a way of easily extracting these information to a txt file or similar? The outputs I found are either in xlm or the single txt files for every sample (in the merged one, there are a lot of other information, so it is possible to read this, but seems unnecessarily cumbersome to extract it from there).
Hello.
Thanks for taking the time to comment. It is really nice to read what you have to say.
The results you want are already there, but make sure that in the Options setting of your method (the last tab) you have enabled all the outputs. That is the default setting so they should be on already.
Below the SpecProcResults folder there are 2 sets of data (but unless you go looking for it you would only see one of them through the web page view). In addition the most recent processed results are copied into the raw folder. The \SpecProcResuts\ path contains both xml, txt and all previous processing. The Raw folder only has the text version of the most recent.
If your project was called xyz then you would have
...\SpecProcResults\xyz_Files\
and
...\SpecProcResults\xyz_Merged\
Somewhere below these paths are the files you are after. When you have a lot of processing results in there it is a bit of a mind melter to navigate to the one you are actually after.
I should have added that the text files look overwhelming in Notepad, but they are set up so they drop straight into Excel. The column layout is predictable so once you know what columns to hide it becomes easily repetitious. The files (both text and xml) contain a lot of information as behind the scenes there is a lot of information (!) and it isn't possible to predict which bits are important to any particular user. So the approach was to stick it all in a file and let you (the user) get what you want with excel.