Just recently, on two different instruments, when we go to Analyze - Replace Calibration - for the CC, it updates the CC level, but DELETES one of the cal levels from every compound. It never did this before, and now we can't get it to not do it. Any h

We open and apply our latest .M file. Then when we try Analyze->Replace Calibration->All cmpds / CC level only, it does that update but drops a cal level from every compound. It is doing this on two different instruments. We've tried rebatching, running the CC from a brand new sequence, applying a method from a batch file where updating the CC does NOT cause a cal point to drop. We've gotten around it by Add Calibration->CC and then going into "Edit" Method and deleting the previous CC level line from EVERY compound... It never used to do this, and it its (thankfully) not doing it still on our Volatiles method with the twice the compounds!

We're not sure if something got corrupted or some setting got turned on inadvertently, or if there's some hidden column somewhere telling it to do that?! 

Simply confused!

Parents
  • Hello ,

     

    Based on your descriptions and tags this appears to be an issue with MassHunter Quant, correct? Which software revision and instrument version are you using?

     

    I will say in general if levels are being deleted when analyzing or updating curves it may indicate that that there is a mismatch between the levels present in the current batch and the levels present in the method being brought in. You may also want to make certain there are no mismatches in the level names. For example, I2, l2, and 12 may look similar, but if the names don't match exactly character for character between the batch table and the method then the level will not be used. 

Reply
  • Hello ,

     

    Based on your descriptions and tags this appears to be an issue with MassHunter Quant, correct? Which software revision and instrument version are you using?

     

    I will say in general if levels are being deleted when analyzing or updating curves it may indicate that that there is a mismatch between the levels present in the current batch and the levels present in the method being brought in. You may also want to make certain there are no mismatches in the level names. For example, I2, l2, and 12 may look similar, but if the names don't match exactly character for character between the batch table and the method then the level will not be used. 

Children
No Data
Was this helpful?