Wish List for PFE Features

[John Donovan]

Yes that's correct - because otherwise calczaf gives an error message for the duplicate Ca stating that it has no counts. Thus I found the way around this is to delete this line and correct the element number. I don't know if there is a better way of doing this

Ok, great.  I can fix this easily in the PFE output code.  Just wanted to make sure I wasn't missing anything else.  I'll have this fixed for you tomorrow!
john

[John Donovan]

Hi John,

Yes that's correct - because otherwise calczaf gives an error message for the duplicate Ca stating that it has no counts. Thus I found the way around this is to delete this line and correct the element number. I don't know if there is a better way of doing this

Thanks

Ben

Hi Ben,
Ok, I added code to check for aggregate mode and duplicate elements when outputting the CalcZAF format. I'm uploading the update today (no bump in version number so still 11.8.0), but it should be ready for you by the time you wake up tomorrow (or Monday!).

Here is an example of measuring Ti on all 5 spectrometers, first with no aggregate mode:

2, 7, 20, 40,"1920 sec on SiO2",-10205,-546, 42
1,"","",0.0,"","",0.0
"ti","ka", 1, 2, 922, 0,-5.200063E-07, 0
"ti","ka", 1, 2, 922, 0, 5.729499E-06, 0
"ti","ka", 1, 2, 922, 0, 3.795455E-07, 0
"ti","ka", 1, 2, 922, 0,-9.59413E-07, 0
"ti","ka", 1, 2, 922, 0, 7.634579E-06, 0
"si","", 1, 2, 0, 46.743, 0, 0
"o","", 1, 0, 0, 0, 0, 0


and again, with aggregate mode:

2, 3, 20, 40,"1920 sec on SiO2",-10205,-546, 42
1,"","",0.0,"","",0.0
"ti","ka", 1, 2, 922, 0, 2.77707E-06, 0
"si","", 1, 2, 0, 46.743, 0, 0
"o","", 1, 0, 0, 0, 0, 0


This works for both all data lines or just the average.
john

[Ben Buse]

Thanks John, all working well - that's great saved me a lot of time editing scripts

Ben

[John Donovan]

1) We talked about this off-line, but could the "Stop" button in the Digitize Image window be greyed out/inactive for the JEOL 8x00's, at least until that command is working? I try to scare my users enough that they don't click it, but it's also surprisingly easy to click it by accident, and some of them don't scare easily.

The button has been removed in the latest version of PFE- at least until we get the command working.

2) Would it be possible to output detection limits in units other than wt% elemental? Specifically, would it be possible to add an option to the Output - Save User Specified Format Output window to export detection limits in wt% oxide as well as, or instead of, wt% elemental?

Almost everything is possible!     

Yes, I can add this.  Give me a few days...
john

[John Donovan]

Much appreciated - no rush for either item.

Thanks much,
OKN

Hi Owen,
OK, I added detection limit output in oxide wt% to the user specified format in PFE.

Update to v. 11.8.2 and you should be good to go.
john

[Anette von der Handt]

Hi,

this is coming from the training at Carnegie: When doing combined conditions, it would be good if one could define delays (settling time) for changes in accelerating voltage and beam current (+ beam diameter??)

A crude drawing for an example dialog is attached.

[Anette von der Handt]

And this one is from me:

Would it be possible to add a "Clear current element setup" button in the element/cations dialog? This would allow to delete all elements in the current setup to start from scratch. I do that quite often for my major element/trace element setup that I combine later in post-processing.

Serving suggestion attached.

Thanks!

[John Donovan]

this is coming from the training at Carnegie: When doing combined conditions, it would be good if one could define delays (settling time) for changes in accelerating voltage and beam current (+ beam diameter??)

Hi Anette,
There are already delays defined for changing keV and beam current (and I think beam size ) in the probewin.ini file.   Will that work?
john

[John Donovan]

Would it be possible to add a "Clear current element setup" button in the element/cations dialog? This would allow to delete all elements in the current setup to start from scratch. I do that quite often for my major element/trace element setup that I combine later in post-processing.

There is already a Remove All Elements From Sample button in the Element Setups dialog.  Will that work?
john

[Anette von der Handt]

Hi Anette,
There are already delays defined for changing keV and beam current (and I think beam size ) in the probewin.ini file.   Will that work?
john

Hi John,

I would say that this is not visible enough for the user. My suggestion would be to add those fields to the combined conditions dialog and populate the fields with the defaults from the probewin.ini field. Is that possible?

[Anette von der Handt]

There is already a Remove All Elements From Sample button in the Element Setups dialog.  Will that work?
john

Uh, I learned something new here, I was not aware of that option. I would say it would be great if you could bring that button into the "Acquired and Specified Elements" dialog too. If even I was not aware of it I would say it is too well hidden. And yes, that is exactly what I am looking for.

Thanks!

[John Donovan]

Hi Anette,
There are already delays defined for changing keV and beam current (and I think beam size ) in the probewin.ini file.   Will that work?
john

Hi John,

I would say that this is not visible enough for the user. My suggestion would be to add those fields to the combined conditions dialog and populate the fields with the defaults from the probewin.ini field. Is that possible?

Hi Anette,
You're saying you want the user to be able to edit these delays within the application?    It would certainly be possible, though maybe in the Acquisition Options would be a better place?  Curious why you don't just want to modify these delays in the probewin.ini file until they work properly and leave it at that.  This would be for the delays *after* setting the column parameters? Correct?

May I ask why you want to change these delays in the application?    There is already a TDI incubation and/or carbon decontamination delay in Acquisition Options...
john

[John Donovan]

There is already a Remove All Elements From Sample button in the Element Setups dialog.  Will that work?
john

Uh, I learned something new here, I was not aware of that option. I would say it would be great if you could bring that button into the "Acquired and Specified Elements" dialog too. If even I was not aware of it I would say it is too well hidden. And yes, that is exactly what I am looking for.

Thanks!

Hi Anette,
I can't easily move the Remove All Elements" button to the Analyze and Specified Elements dialog as there is no room (when loaded from the Analyze! window) without a big re-arrangement of the controls.

Let me think about it some more, but in the meantime "now you know!" (where that button is).   
john

[Anette von der Handt]

Hi Anette,
You're saying you want the user to be able to edit these delays within the application?    It would certainly be possible, though maybe in the Acquisition Options would be a better place?  Curious why you don't just want to modify these delays in the probewin.ini file until they work properly and leave it at that.  This would be for the delays *after* setting the column parameters? Correct?

May I ask why you want to change these delays in the application?    There is already a TDI incubation and/or carbon decontamination delay in Acquisition Options...
john

Hi John, I guess it actually does not make much sense to have them changeable on a sample per sample basis. How about having them on display though as in my dialog layout proposal but not editable. This would accomplish both that the user would be aware that there is a delay being applied upon changing conditions and allow that the values can be critically evaluated (whereas otherwise they would be "hidden" in the probewin.ini file).

What do you/everyone think?

[Anette von der Handt]

Hi Anette,
I can't easily move the Remove All Elements" button to the Analyze and Specified Elements dialog as there is no room (when loaded from the Analyze! window) without a big re-arrangement of the controls.

Let me think about it some more, but in the meantime "now you know!" (where that button is).   
john

Ah yes, I see. Ok, so I guess for now it is a "tips and tricks" entry until some later time potentially.