-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identical wavelength for different transitions in the same file #48
Comments
Hi @fsciortino , thanks for the update on Using it raised one error, that I corrected on my fork of aurora, and then a second error occured, that I also corrected on my fork. Then it works, but I started thinking that when a line wavelength is shifted, the code should raise a warning so the user knows it, so I implemented the warning. Using that version of the code revealed that there are actually many lines with redundant wavelengths. So I implemented a more synthetic warning that is raised only once and gives the list of all redundant wavelengths (ordered according to the wavelength). For file
I see at least 2 causes for concern:
Thoughts on this:
Proposition:
|
Motivations:
aurora
load spectral lines fromADAS
adf15
files into a dictionary where they are sorted by wavelength (i.e.: the wavelentgth, as a float, is the key of the dictionary)Current behaviour:
On python
3.7.11
, the behaviour when fed several times the same key is that thedict
will only retain the last provided value:It means that in its current version,
aurora
, when confronted with several transitions of identical wavelengths, will only provide the one it encounters last in the file.Example:
Ar16+
, when ones looks for thek
lines, it turns out a different transition with the same wavelength (3.9900 A
) exists in the same filepec#ar15.dat
:The text was updated successfully, but these errors were encountered: