docs: organise campaigns around the published records, drop the snaps… - #57
Merged
Merged
Conversation
…hot page A campaign page now exists to say how the calculations behind a published record were made and how to reproduce them. Two campaigns, three records: the SCF k-point sweep published 52713-55d86 and mcpnq-g1j55, which are two views of one body of calculations and are presented together, and the nscf band campaign published r3byg-xp284, which gets a page of its own. results.md is deleted. A dated snapshot of an in-flight campaign -- workchain counts, ultra rate, regenerated local files -- is our operational record, not something a reader of the site needs. The nscf record is live, so its placeholder link is replaced. Two accuracy fixes while reorganising: the SCF campaign page states that the criterion is the whole remaining tail, which is stricter than the "three consecutive" wording in 52713-55d86's own README; and the convergence reference now says its three thresholds come from campaign.yaml and differ from the package defaults.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…hot page
A campaign page now exists to say how the calculations behind a published record were made and how to reproduce them. Two campaigns, three records: the SCF k-point sweep published 52713-55d86 and mcpnq-g1j55, which are two views of one body of calculations and are presented together, and the nscf band campaign published r3byg-xp284, which gets a page of its own.
results.md is deleted. A dated snapshot of an in-flight campaign -- workchain counts, ultra rate, regenerated local files -- is our operational record, not something a reader of the site needs.
The nscf record is live, so its placeholder link is replaced.
Two accuracy fixes while reorganising: the SCF campaign page states that the criterion is the whole remaining tail, which is stricter than the "three consecutive" wording in 52713-55d86's own README; and the convergence reference now says its three thresholds come from campaign.yaml and differ from the package defaults.