-
Notifications
You must be signed in to change notification settings - Fork 16
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
More robust seedname.wout parser #1
Comments
I think it's a bit more complex than that... the problem is that sometimes there are no spaces between coordinates!! (for long numbers starting with a minus) What about adding a new output to W90 (if it's not already in the tb_parameters) with the centers spreads etc instead of trying to parse the wout? |
Is there a good library to produce structured output (csv, xml, json, yaml) from Fortran? If so, I would argue for using that when creating a new output file. Otherwise we'll have to write yet another output parser.. |
Maybe things like YAML are simple enough to be written even without a library? (I hope...) |
Or a CSV with just |
after the comma (for many-digit numbers). Not perfect, but good workaround (also for #1) that does not require to change Wannier90.
I would consider this issue more general, and improve the names and parsing of the output. |
@normarivano could you report here the table that we started discussing, with the suggested changes to the parser key names, for discussion with the others? |
I attach hereafter the table for the parsing of the standard output file. We propose some changes for the keys' names to be implemented within this release. Can you give me some feedback as soon as possible? Thank´s a lot.
|
I´m also going to open an other issue (not in Milestones) in which we can discuss additional information to parse for the future. Me and @qiaojunfeng already started discussing that. |
Looks all good to me 👍 |
Thanks a lot! Looks good to me as well. Very good also to go back to UK spelling considering this is what the W90 code uses. Just a couple of comments of things I would change:
|
All good for me - I close the issue. |
I reopen it - let's close it when we have the PR that changes the names |
We should use regular expression instead of split&strip to parse x y z and the spread at each iteration.
The text was updated successfully, but these errors were encountered: