Merge lp:~nickpapior/siesta/4.0-nrtab into lp:siesta/4.0
Proposed by
Nick Papior
Status: | Merged |
---|---|
Merged at revision: | 560 |
Proposed branch: | lp:~nickpapior/siesta/4.0-nrtab |
Merge into: | lp:siesta/4.0 |
Diff against target: |
179 lines (+51/-13) 7 files modified
Docs/compatibility.tex (+3/-5) Docs/siesta.tex (+14/-0) Src/Makefile (+1/-1) Src/new_matel.F (+10/-3) Src/read_options.F90 (+16/-2) Src/siesta_options.F90 (+6/-1) version.info (+1/-1) |
To merge this branch: | bzr merge lp:~nickpapior/siesta/4.0-nrtab |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alberto Garcia | Needs Fixing | ||
Review via email: mp+342574@code.launchpad.net |
Commit message
Enabled old NRTAB behaviour via pre-processing flags.
By specifying SIESTA_
NRTAB behaviour which may be used to compare against older
siesta versions.
The compatibility.tex document has been updated to reflect this.
Description of the change
I simply added what we discussed at Slack (changing the pre-processor name).
To post a comment you must log in.
Please forgive me for having second (third?) thoughts about this. An increasing number of users now depend on having SIESTA installed by a third person, be it a supercomputer center's staff or some grumpy sysadmin who cannot be counted on to provide a full range of SIESTA versions with all possible preprocessing options...
Thus, those users will be most likely locked into the new default value for NRTAB, and will be unable to reproduce older results with the new version.
This problem is not restricted to this issue, of course.
I have tentatively produced a patch that will make NRTAB configurable at two levels: a "legacy" switch to reproduce old results, and a full setter for people who want to try different values (not all of them would be allowed, as NQ must be compatible with NRTAB...).
(I will attach the patch somehow)