OpenLab Chemstation C.01.10 Dual FID Report

I am using OpenLab Chemstation C.01.10 on an 8890 with dual FIDs. I was trained on HP's version of Chemstation that reported both detector quant amounts in one row for precision purposes. It made it 10x easier to review data and confirm sample concentrations for my HAA5 analysis with both signals on the same row. I have been fiddling with the report designer, but I cannot seem to figure it out. Is it possible for the software to report in the manner described?

Parents
  • Hello,

    Are you looking for a single injection report or is this for a summary report? When you setup the calibration table are you doing main peak and qualifiers or are the compounds calibrated separately in the 2 signals. How many compounds are in your calibration table? 

    Marty Adams

  • Hello,

    Is this the type of table you are looking for?

    Marty Adams

     

  • Hello,

    It is a single injection report. The compounds are calibrated separately on each signal. I have 18 compounds per signal (2 are ISTDs).  I am essentially looking for something like the attached picture, if possible. 

  • Hello,

    That looks more like MSD Chemstation than OpenLab Chemstation or the previous equivalent so that is likely the difference in the reporting. You would need to create a hidden table at the top for the second signal. in the table, you could then store the RT, Area, and Conc in a variable keyed on compound_name. Those variables could then be displayed in a visible table below filtered for signal A so you could have 2 values per line. 

    Marty 

  • Hello,

    See the attached screen capture video for an example of the request report modifications. Please note that when I talk about and name the variables peak B I am referring to the compounds in the B signal channel. Also, the example was done in CDS 2.x IR but the same process can be used in Chemstation IR. 

    Marty

    /cfs-file/__key/communityserver-discussions-components-files/26/2024_2D00_01_2D00_18_5F00_15_2D00_41_2D00_13.mp4

  • Marty,

    I appreciate you taking the time to provide the video and thorough instructions. I was able to follow along with no issue and essentially match what you had done throughout. The one difference was I used the Short ISTD as a template. I'm not sure if that will make a difference in my follow up question. I am applying the modified report to my quantitation method, but I am getting different reports in the Data Analysis tab and the Review tab. I've attached a copy of both. The Review tab report looks exactly how I want it, but for some reason is not pulling data over. The Data Analysis report is, well, a mess. It isn't hiding tables at all. I typically review data in the Data Analysis tab and generate a report by using the Classic Quantitation option. I changed my report to Intelligent Report and selected the file, as well. Do you have any suggestions to remedy this?

  • Marty,

    It seems the core of the issue is that my compound names do not pull like your compounds and information (RT, area, amount) do in your demo. I have the calibration table established on both detectors and with the same exact name. If I have to generate reports in the review tab from now on to accomplish this style of reporting, that's perfectly fine. So, that may not be as big of an issue. 

  • Hello,

    Starting with the ISTD report should not change anything from the example. One possible issue with the report in data analysis would be you need to update the report template. If you are using result sets in Chemstation, which is the default, the software saves the template in the result set. So, for example, if I add an IR template to my method called Test.rdl and run or reprocess the result set a copy of the template is now inside the result set. Any further reprocessing or report creation in DA with that data uses the copy of the template inside the result set. This mean if you now edit the master test.rdl template, it will not match the copy inside the result set. However, if you create reports in the review mode it will use the edited template, as it always use the master templates. To update the report template in the result set you need to select it again in the specify report section of the method and overwrite the copy in the result set. 

Reply
  • Hello,

    Starting with the ISTD report should not change anything from the example. One possible issue with the report in data analysis would be you need to update the report template. If you are using result sets in Chemstation, which is the default, the software saves the template in the result set. So, for example, if I add an IR template to my method called Test.rdl and run or reprocess the result set a copy of the template is now inside the result set. Any further reprocessing or report creation in DA with that data uses the copy of the template inside the result set. This mean if you now edit the master test.rdl template, it will not match the copy inside the result set. However, if you create reports in the review mode it will use the edited template, as it always use the master templates. To update the report template in the result set you need to select it again in the specify report section of the method and overwrite the copy in the result set. 

Children
  • Marty,

    I fixed the issue between Review and DA reports per your recommendation, so they are now matching. I am still not having my data pull to the report for some reason. I will have to investigate why that is the case. I'm not sure why there would be a discrepancy with this when it pulls in classic reporting. It will not pull compound names, RTs, etc. using any template, let alone the one that I made following your demo. 

    Nick 

  • Nick,

    Okay that is strange did you reprocess the result set after making the changes to the method? IR reports work with the ACAML file that is created during reprocessing. If you have direct access to the data, you can check for the presence of the sequence.acaml. 

    Marty Adams

  • Marty,

    I had not done that. I had been using the recalculate mode when looking at data. I have done that in the past so I could use a unique quantitation method, which may or may not be the issue. However upon reprocessing, the file was created, but the report is still lacking compound names, RTs, etc. 

    Nick 

  • Hello,

    You still cannot create any IR report even the short_area report? Do you get any kind of message about there being no ACAML file for some of the injections when creating a report in the review mode? Can you check the method and make sure you have standard data processing enabled? You are using the reprocessing workflow not batch analysis, correct? 

    Marty Adams

  • Marty,

    Standard Data Analysis is checked. I feel like I'm missing something simple at this point. ACAML files are being created when I reprocess the data. I am able to use other templates, and the data pulls into that. The compound names and corresponding info are not being pulled into the tables I made using your demo where I added two and hid the top table. I have tried the data analysis in the reprocess and recalculate modes. I hope that addresses your question properly. In the report, my chromatograms are labeled with the peak names, furthering my confusion. 

    Nick 

  • Nick,

    I am not sure what you mean by the chromatograms are labeled with your peak names. Do you mean the chromatograms show the labeled peaks, so you know they are identified correctly? My guess would be the filters you setup are not correct. My video was just an example, you needed to setup the filters based on the signal names in your results. If you followed my example and made the correct updates, you would have setup 2 report parameters with strings like FID1A and FID1B and then setup filters on the tables with signal_name = reportparameter name. You can try removing the filters on the tables to see if the compounds show up in the tables with no filters. If so then the filters are wrong. You need the exact signal name in the filter. See below for an example in Chemstation. I hardcoded the filters in the example and did not use the report parameter. 

    Marty

     \

Was this helpful?