Another interesting thing

[Malcolm Roberts]

It's been so quiet recently that I cannot resist this.
1) create a new PfEPMA file
2) Analyse and add new sample
3) load file set and choose a previous analytical file.
4) add/remove standards and go ok.
5) note that the sample now specified is not your unknown but the last standard in your list.
6) add new sample - now, this one is called "wavescan sample" even though it is marked as an unknown.

Now if you use this set up in probe for image and select this unknown as the sample for quantification, it will not allow you to use it, because even though you specified unknown sample, it is logged in the .mdb as wavescan. If, however, you turn round and rename it, all is good.
Why is an unknown being recorded as wavescan? Why does add new sample default to a standard after adding/deleting standards?

Anyone else noticed this?
Cheers,
malc.

[John Donovan]

It's been so quiet recently that I cannot resist this.
1) create a new PfEPMA file
2) Analyse and add new sample
3) load file set and choose a previous analytical file.
4) add/remove standards and go ok.
5) note that the sample now specified is not your unknown but the last standard in your list.
6) add new sample - now, this one is called "wavescan sample" even though it is marked as an unknown.

Now if you use this set up in probe for image and select this unknown as the sample for quantification, it will not allow you to use it, because even though you specified unknown sample, it is logged in the .mdb as wavescan. If, however, you turn round and rename it, all is good.
Why is an unknown being recorded as wavescan? Why does add new sample default to a standard after adding/deleting standards?

Yes, I'd noticed that too. I think it is easy to fix the wavescan sample issue, so I will migrate that to the top of my "to-do" list, but to answer your second question: the reason the app switches to a standard sample after you add a standard, is because the app is assuming that if you added a standard you might want to run it manually next. Just tryin' to be helpful!   

[Malcolm Roberts]

Thanks John....... I have busted into the .mdb file to fix this up before PI, but that's not "really" the "right" way to do it eh?

[UofO EPMA Lab]

Thanks John....... I have busted into the .mdb file to fix this up before PI, but that's not "really" the "right" way to do it eh?

By "I have busted into the .mdb file to fix this up" I assume you mean you manually edited the MDB file in Access?

Yeah, probably not a good idea in general...

[UofO EPMA Lab]

1) create a new PfEPMA file
2) Analyse and add new sample

I think you mean open the Acquire! window and then click the New Sample button?

3) load file set and choose a previous analytical file.
4) add/remove standards and go ok.

Just FYI, there is no need to "Add/Remove Standards" if you are loading a File Setup from a previous run.  The software will automatically add all the standards you need to the current run (and optionally the standard intensities from that run as well).

5) note that the sample now specified is not your unknown but the last standard in your list.

As mentioned previously, this is a feature, not a bug.   

6) add new sample - now, this one is called "wavescan sample" even though it is marked as an unknown.

Yes, I see this and will fix it ASAP.

Now if you use this set up in probe for image and select this unknown as the sample for quantification, it will not allow you to use it, because even though you specified unknown sample, it is logged in the .mdb as wavescan. If, however, you turn round and rename it, all is good. Why is an unknown being recorded as wavescan?

Again FYI, you can use any standard or unknown in your MDB file as the basis for x-ray map quantification in CalcImage so this should not present a problem. Yes, the app incorrectly *names* the new sample "wavescan sample", but as you say, it is actually an unknown, so just change the name and all is good.

[John Donovan]

Now if you use this set up in probe for image and select this unknown as the sample for quantification, it will not allow you to use it, because even though you specified unknown sample, it is logged in the .mdb as wavescan. If, however, you turn round and rename it, all is good.
Why is an unknown being recorded as wavescan?

OK, so by saying Probe Image will not allow you to "use it", you mean the Read ELM buttons don't give you want you would expect?

If, so, this really doesn't have anything to do with the sample name, or even sample type. It has to do with what were the last elements that were "set" in PFE.

The easiest way to set the spectrometer settings (on and off-peak positions, elements, x-rays, etc.) is using this feature:

http://probesoftware.com/smf/index.php?topic=42.msg581#msg581

[Malcolm Roberts]

Hi John...
Wrong stage of the operation.....My fault.... I should have said "CalcImage" and not PI......
Cheers,
malc.

[John Donovan]

OK, the default sample name (when there are no samples) issue is fixed, so an update should prevent the problem you are seeing in CalcImage.