Empower: Can I run sample sets for two different projects?

[Psyentist]

Good morning.

I've been using Empower for a number of years now, and I have run multiple sample sets consecutively within a project many times. I've never had to run two sample sets associated with different projects back to back. The mobile phases are the same for both methods, but the methods use two different columns, so I'd like to set up:

Project A, Sample set A, Column A
to run back to back with
Project B, Sample set B, Column B

It seems like it should be possible, but I don't quite know how to go about it.

Thanks in advance.

[Hollow]

I can't remember if I ever did this, but would not have any concerns.

If you want to be sure, why don't you programm two test sets in Project A and B with blank injections (or equlibrate) for 1 min or so.

[Psyentist]

I opened two acquisition windows, one in each project. I created and initiated sample set A in project A. I then went to the acquisition window for project B and saw the UV and pressure trace were active (the UV trace had a gray background instead of white, perhaps indicating it's not for the active project?). I created sample set B and initiated it. It went into the queue, and I can see both sample sets in the queue regardless of which acquisition window I look at.

[aceto_81]

Once I had to do multiple injections from the same vial with intervals of 4 hours.
I had to do this for different vials, for different projects.

What I did was setting up each injection in another sample set, and madeup a sample set list in project A.
Then I went to project B, made another 8 sample sets.
The I arranged all the sample sets on the right place: alternating project A and project B.

After 24 hours, all my samplesets were finished, in the right projects!


Ace

[DR]

Personally, I'd be inclined to run it all in one project, then copy the appropriate set(s) into the other project, if that's where others need to be able to find them.

[Psyentist]

The second sample set is now running, and it's properly storing the data in the correct project.

DR: It would be a bit of effort to copy the methods from project B to project A just to be able to run sample set B in project A only to have to copy the results back to project B. Then the data is still hanging around in project A. It can be deleted, but it seems like far too much effort when one can do what I did and have it work.

[Psyentist]

Interesting development with this situation. I just went to remove column A from the system and discovered that sample set B, method B, was using column A. I immediately stopped the analysis and investigated. In the instrument method, the column selector was correctly defined. What could have gone wrong?

[Hollow]

In the instrument method, the column selector was correctly defined. What could have gone wrong?

what did you specify for the column selection in the sample set?
if there was another information there, there might be a conflict leading the software to the wrong column (The help sais that the position should be selected either in the instr.meth or the sample set but not both).

For me, I set the column pos in the instr.method to "no change" and select the position with an equilibrate step in the sample set.

Anyway, if no position (no change) was selected in the sample set so as it should use the pos from the instr.method, then this sounds like a bug and should be reported to waters.

[Psyentist]

And I've learned something today. I was not aware that you could specify the column in the sample set.

I have checked the sample set, the Condition Column (first line) has the position "No Change". Every other line has this grayed out. This is also the case in the first sample set. So it should take the position from the instrument method.