Karen01. Wow, you do seem frustrated. It sounds like no one ever put aside an hour or so to give you a basic overview of ChemStation for HPLC software (it would help to know which revision you have and with what instrument model as the graphical interface has undergone some changes over the past twenty years).
The most recent one. The HPLC was installed about 6 weeks ago, 1 week before before i started... AND no one there knows how to run it. They just don't like Water's for some reason.
Perhaps consider taking a class in learning how to use the software.
None scheduled any time soon.
It is very logically constructed (but not perfect, what is ?).
Over the years writing in-house software I have learned that when it comes to user interfaces:
1) Logical alone does not a good user user interface make
2) People think differently
3) power users have very different ideas about good user interfaces than basic users... and it's still based on how they think individually!
The way i think, I took to the Water's database way like a duck to water from day 1.
The trick is to quickly get oriented where the important things are. *Among other things, I train people in how to use a wide variety of chromatography software packages and ChemStation is by far the easiest package to get someone up and running on.
If you mean getting people injecting samples I agree. If you mean easily doing a lot of non trivial non routine data stuff ... Well so far I am very skeptical.
In one day I can usually teach them practical information that would take them at least one to two years to learn on their own.
<smile> If I had a solid uninterrupted QUIET (the lab is noisy) couple of days, I could pick most of it up on my own I think... but so far I have not had that.
Knowledge is a powerful thing and it helps you do your job better too.
I agree. Using Empower i was able to automate much of the workflow of my last lab (which has some unusual requirements) and using the power provides Database approach I was able to do sophisticated ad-hoc stuff quickly.
A few free tips: Basically you spend most of your time in either the 'Instrument' View Menu (which has everything you need to set-up and run Methods or Sequences) or the 'Data Analysis' View (which has everything needed for Calibrations, Integration, Reports and overlays...) Yes, data file (or signal) overlays are very simple and quick as 'consumer product guy' mentioned.
<smile> Picking the injections and channels (signals) you want with file names like that is not simple in practice for me. My brain does not digest strings of numbers like that.
Glad to hear I can get it to show me more info ... But I really wish I could see injections (with sample names) from multiple sequences in the navigation pane at once ... If only the sequences in the navigation pane had disclosure widgets!!!
BTW I hate toolbars and even in Empower i always used the menus instead of the toolbars...
Just load the file(s) or specific signal(s) one at a time.
I was trying to do that, but as group, as i would do it in Empower where i could see all injections (and sample names) across 'sequences'...
The navigation pane only showed sequences and would not show the the individual injections ( would noy open in tree form) in a sequence to control click on...
I could right click on a sequence and then choose to overlay injections from within that sequence, but for the life of me I could not figure out how to pick injections across sequences. The MDI interface just hid too much to realize what was going on when you "loaded".
*Also, turn on the 'File Info' button (I think that is the name used, but I am not looking at it right now). This displays the information about each data file BEFORE you LOAD it so you can see the sample name, date, signals and other sample info entered by the operator. Very handy (always fill in the sample comment information box when running a Method and the Method Information Box too).
I've not been doing that... Empower requires you to create a specific name for each run to start the run... I did not connect comments and method information with run ID's.
As far as sample names go, well that is up to the operator and also dependent on the version of ChemStation ('B.01.01' rev introduced long file names).
Sample names are not a problem ... it's having to deal with data file name as principle ID for a chromatogram. I never want to have to see/deal with raw file names... Why should I have to care about such things? That's where Empower really shines.
I personally use names that directly relate to the sample name and then store them in folders which relate to the compound, study type or group that the sample goes in (what ever makes the most logical sense so I can find them quickly later on).
That is what I used projects for on Empower...Once a project was set up I never had to deal with paths.
Good luck and let us know how it all works out.
I'll learn it.
It's hard to find quiet time at work to play with it. They also have an OLD water's system that uses Empower, so i have to go back and forth between Empower and Chemstation... Which makes it more difficult.
Thanks for your help... Hopefully tomorrow I'll have better luck with it!!!
- Karen