Page 1 of 1

Retention time locking - new method

Posted: Thu Oct 03, 2019 3:37 pm
by kristin
I had a method running with retention time locking. That method got corrupted, and I had to rebuild it from default. My question is - is there a way to transfer the retention time lock data to the new method, or do I have to redo it? The method is the same, and no column work was done so there is no retention time changes as yet. I am running on MassHunter 8.0

Thanks!

Re: Retention time locking - new method

Posted: Tue Oct 08, 2019 2:19 am
by Henrylozano
I had a method running with retention time locking. That method got corrupted, and I had to rebuild it from default. My question is - is there a way to transfer the retention time lock data to the new method, or do I have to redo it? The method is the same, and no column work was done so there is no retention time changes as yet. I am running on MassHunter 8.0

Thanks!
I think it's not possible, it's time to recreate it.

Re: Retention time locking - new method

Posted: Fri Nov 29, 2019 3:30 am
by aldehyde
Hi, in a recent change (B.07.06 SR1) a feature was added that would allow you to bring the data files into the method, and then recalculate the RTL calibration.

What you would do is navigate into the method.M folder and create a folder called RTLOCK, then navigate to your old method and copy the 5 RTLOCK.D data files and paste them into the newly created RTLOCK folder.

Once the data files are there, go into Acquisition and choose Method > Acquire RTLock Calibration Data.

If you have B.07.06 SR1 or later the software will recognize that data files are present and will ask "Do you want to use the data files or acquire new data?" If you use the existing data, it will re-calculate the calibration.

This is particularly helpful if something annoying happens like the power goes out after injection 4. You could create a method with the right flow rates and acquire that missing RTLOCK5.D file, and then re-trigger the calculation. Alternatively, if you have all your data files but make a mistake or accidentally cancel the calibration you can restart it without having to re-acquire the data files.

Good luck!

Re: Retention time locking - new method

Posted: Thu Apr 15, 2021 12:21 am
by LALman
Hi, in a recent change (B.07.06 SR1) a feature was added that would allow you to bring the data files into the method, and then recalculate the RTL calibration.

What you would do is navigate into the method.M folder and create a folder called RTLOCK, then navigate to your old method and copy the 5 RTLOCK.D data files and paste them into the newly created RTLOCK folder.

Once the data files are there, go into Acquisition and choose Method > Acquire RTLock Calibration Data.

If you have B.07.06 SR1 or later the software will recognize that data files are present and will ask "Do you want to use the data files or acquire new data?" If you use the existing data, it will re-calculate the calibration.

This is particularly helpful if something annoying happens like the power goes out after injection 4. You could create a method with the right flow rates and acquire that missing RTLOCK5.D file, and then re-trigger the calculation. Alternatively, if you have all your data files but make a mistake or accidentally cancel the calibration you can restart it without having to re-acquire the data files.

Good luck!
I'm using Chemstation E.02.01 and it will let me save a method that has RTLOCK files under a new name and then I can use them there also. But it will not let me use RTLOCK files copied and pasted into the method tree. Even though my 8260 and BTEX method both use identical aquisition parameters. I can quant an 8260 file as BTEX and vis versa. But I cannot share the RTLOCK files from the 8260 with the BTEX.

Re: Retention time locking - new method

Posted: Thu Apr 15, 2021 7:25 pm
by James_Ball
Hi, in a recent change (B.07.06 SR1) a feature was added that would allow you to bring the data files into the method, and then recalculate the RTL calibration.

What you would do is navigate into the method.M folder and create a folder called RTLOCK, then navigate to your old method and copy the 5 RTLOCK.D data files and paste them into the newly created RTLOCK folder.

Once the data files are there, go into Acquisition and choose Method > Acquire RTLock Calibration Data.

If you have B.07.06 SR1 or later the software will recognize that data files are present and will ask "Do you want to use the data files or acquire new data?" If you use the existing data, it will re-calculate the calibration.

This is particularly helpful if something annoying happens like the power goes out after injection 4. You could create a method with the right flow rates and acquire that missing RTLOCK5.D file, and then re-trigger the calculation. Alternatively, if you have all your data files but make a mistake or accidentally cancel the calibration you can restart it without having to re-acquire the data files.

Good luck!
I'm using Chemstation E.02.01 and it will let me save a method that has RTLOCK files under a new name and then I can use them there also. But it will not let me use RTLOCK files copied and pasted into the method tree. Even though my 8260 and BTEX method both use identical aquisition parameters. I can quant an 8260 file as BTEX and vis versa. But I cannot share the RTLOCK files from the 8260 with the BTEX.
Are you using a compound that is in both methods for the RT Lock data?

Re: Retention time locking - new method

Posted: Mon Apr 26, 2021 9:47 pm
by LALman
I'm using Chemstation E.02.01 and it will let me save a method that has RTLOCK files under a new name and then I can use them there also. But it will not let me use RTLOCK files copied and pasted into the method tree. Even though my 8260 and BTEX method both use identical aquisition parameters. I can quant an 8260 file as BTEX and vis versa. But I cannot share the RTLOCK files from the 8260 with the BTEX.
Are you using a compound that is in both methods for the RT Lock data?
Yes I'm using toluene-d8
I solved the problem by copying to a new name and then deleting all the not BTEX analytes as you suggested.