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
I am trying to do a CRM using multiple charged states of Lithium (Li atom, Li + and Li ++).
So i want to know which is the correct way to do it.
calculate the structure calculations together in a single input file and generate all the cross sections in a single file for all the three charged states. and then in the CRM, call the AddIon function multiple times.
then i am getting an error message like this
I don't understand what this error means?
and the other way i tried is
separately running the structure calculations of each atoms then generate separate cross sections files for each charged states then run the CRM model like this
here i am not getting any error messages.
I want to know which is the right way
The text was updated successfully, but these errors were encountered:
indhusureshiitt
changed the title
confucion in the Addion function to add multiple ions in the CRM
confusion in the Addion function to add multiple ions in the CRM
Jun 26, 2024
I am running this command to include the Li I and Li II ions, and I gave the population densities in this way.
My ground state density of Li I varies like this for the given te and ne grid.
and the ground state density of Li II varies like this
But initially, I gave the ground state density of Li II as zero. How can I interpret this density now? Is it relative to the ground state density of Li I?
so in that case how can i find the actual density of ground state or any other states of Li II?
I am trying to do a CRM using multiple charged states of Lithium (Li atom, Li + and Li ++).
So i want to know which is the correct way to do it.
then i am getting an error message like this
I don't understand what this error means?
and the other way i tried is
here i am not getting any error messages.
I want to know which is the right way
The text was updated successfully, but these errors were encountered: