Skip to content
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

atomic data (photoionization x-sections) for P #674

Open
kslong opened this issue Mar 16, 2020 · 9 comments
Open

atomic data (photoionization x-sections) for P #674

kslong opened this issue Mar 16, 2020 · 9 comments
Assignees

Comments

@kslong
Copy link
Collaborator

kslong commented Mar 16, 2020

I was trying to add PV to our atomic data, but (at least for certain ionization modes, perhaps all) one requires photoionization x-sections. These are netierh in VKFY or Topbase

@kslong
Copy link
Collaborator Author

kslong commented Mar 16, 2020

It looks like the necessary data may be in these papers.

Palmieri+16 - K-shell photoabsorption and photoionisation of trace elements. I. Isoelectronic sequences with electron number 3 ≤N ≤ 11

Mendoza+17 - K-shell photoabsorption and photoionization of trace elements. II. Isoelectronic sequences with electron number 12 ≤N ≤ 18

Mendoza+18 - K-shell photoabsorption and photoionization of trace elements. III. Isoelectronic sequences with electron number 19 ≤ N ≤ 26

and the database for this is here

http://cdsarc.u-strasbg.fr/viz-bin/cat?J/A+A/616/A62

@kslong kslong changed the title atomic data (photoionization x-sections) atomic data (photoionization x-sections) for P Mar 16, 2020
@Higginbottom
Copy link
Collaborator

Hmmmm, OK. When the new data was put in, I certainly tried to keep the ethos going. The intention was that python would read in and default to Topbase PI data if the VFKY wasn't available. Is that not working?

@kslong
Copy link
Collaborator Author

kslong commented Mar 17, 2020 via email

@Higginbottom
Copy link
Collaborator

Ah OK - do you want me to get it in then - or are you OK with putting it in the data repo?

Nick

@kslong
Copy link
Collaborator Author

kslong commented Mar 17, 2020 via email

@kslong
Copy link
Collaborator Author

kslong commented Mar 19, 2020

@Higginbottom So I have made some progress. What is currently happening with verner_2_py.py is that some but all of the x-sections in VY are being used. I also believe there are errors in the file vy_innershell_tab.data, which we use. It contains some x-sections for ions with z that are outside of the range 1-20 or 26. Additional of course, the inner shell x-sections for P are missing. The file that is attached is vy with a final column indicating whether a particular line is used. v means it was use to extend a vfky x-section, i means it's an inner shell transition included in the innershell_tab, and n means not used at all.

foo.txt

@kslong
Copy link
Collaborator Author

kslong commented Mar 19, 2020

@Higginbottom There is now a new vesion verner_2_py.py called xverner_2_py.py, which attempts to deal with the x-sections in VY that were not included in the output previously, either as an addition to a VKFY x-section or as an outershell transition. This allowed me to run an O-Star model with PV. It's routine assumes that any VY transition not identified as an outer shell transition is an inner shell transition, which likely incorrect for atoms that have ion species with nelec not included in your table somehow. We should sort this out, because we will forget if we don;t deal with it in the near term.

@kslong
Copy link
Collaborator Author

kslong commented Mar 20, 2020

@Higginbottom Is there any reason we should not remove the old structures for the VY x-sections and also the code which calculates the x-sections from the formulae, since everything now effectively read in as an array of values. (I have done this on a local branch and as far as I can telll it does not matter). Also, at this point, what is the essential difference between x-sections from the different sources. It must be something in the information we provide as "header" information, and or how they are used.

@kslong
Copy link
Collaborator Author

kslong commented Jun 12, 2020

This is needed for the release paper

@kslong kslong added the high label Jun 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants