You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On another we have the following example:
100Mo++ 4.959043e+01 5.042044e+01 extracted from a Matlab FIG from one the Erlangen atom probe schools, no charge_state_analysis is performed and the charge of ++ discarded, is this because 100Mo is not observationally stable but the shortest half life constraint is infinity? If we want to accept this what is then a good community agreed upon shortest_halflife constraint for the algorithm because every releasing of the constraint would also yield cases for other isotopes that may made other charge state analysis to yield contradictory charge states for the molecular ions and thus the algorithm would decide one cannot range such a molecular ion to a unique charge_state. Tritium is one such case where then an automated analysis of the following line for hydrogen 1.01 0.9023523209398241 0.8355030737479705 1.1543789326510643 from Erlangen's pyccapt ranging would also suggest a triply-charged tritium ion falling in the range despite with very low abundance values, do we want this or not?
The text was updated successfully, but these errors were encountered:
On another we have the following example:
100Mo++ 4.959043e+01 5.042044e+01 extracted from a Matlab FIG from one the Erlangen atom probe schools, no charge_state_analysis is performed and the charge of ++ discarded, is this because 100Mo is not observationally stable but the shortest half life constraint is infinity? If we want to accept this what is then a good community agreed upon shortest_halflife constraint for the algorithm because every releasing of the constraint would also yield cases for other isotopes that may made other charge state analysis to yield contradictory charge states for the molecular ions and thus the algorithm would decide one cannot range such a molecular ion to a unique charge_state. Tritium is one such case where then an automated analysis of the following line for hydrogen 1.01 0.9023523209398241 0.8355030737479705 1.1543789326510643 from Erlangen's pyccapt ranging would also suggest a triply-charged tritium ion falling in the range despite with very low abundance values, do we want this or not?
The text was updated successfully, but these errors were encountered: