-
Notifications
You must be signed in to change notification settings - Fork 37
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
Adding the trajectories endpoint to OPTIMADE #377
Open
JPBergsma
wants to merge
70
commits into
Materials-Consortia:develop
Choose a base branch
from
JPBergsma:JPBergsma_add_Trajectories
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Adding the trajectories endpoint to OPTIMADE #377
JPBergsma
wants to merge
70
commits into
Materials-Consortia:develop
from
JPBergsma:JPBergsma_add_Trajectories
Conversation
This file contains 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
JPBergsma
force-pushed
the
JPBergsma_add_Trajectories
branch
3 times, most recently
from
July 21, 2021 15:15
08f1bf7
to
b907b2c
Compare
JPBergsma
commented
Jul 21, 2021
JPBergsma
force-pushed
the
JPBergsma_add_Trajectories
branch
from
July 21, 2021 15:48
b907b2c
to
716ad2e
Compare
JPBergsma
added
PR/major-edits
type/proposal
Proposal for addition/removal of features. May need broad discussion to reach consensus.
labels
Jul 21, 2021
JPBergsma
commented
Jul 22, 2021
JPBergsma
commented
Jul 22, 2021
ml-evs
reviewed
Jul 22, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the hard work on this @JPBergsma!
My comments below are mostly around maintaining our compliance with the JSON:API format.
JPBergsma
force-pushed
the
JPBergsma_add_Trajectories
branch
from
July 22, 2021 10:33
716ad2e
to
7c1b646
Compare
Placed all sentences on seperate lines.
JPBergsma
force-pushed
the
JPBergsma_add_Trajectories
branch
from
July 22, 2021 10:57
7c1b646
to
a291b59
Compare
JPBergsma
commented
Jul 22, 2021
ml-evs
reviewed
Jul 22, 2021
…eferences for frames.
JPBergsma
commented
Jul 26, 2021
…lso possible to do this via the next field in the links field of the JSON response.
Can we add an endpoint for bulk downloads? |
…gsma/OPTIMADE into JPBergsma_add_Trajectories
vaitkus
reviewed
Jun 16, 2023
vaitkus
reviewed
Jun 16, 2023
Co-authored-by: Antanas Vaitkus <[email protected]>
… can contain multiple values.
vaitkus
reviewed
Jan 17, 2024
Co-authored-by: Antanas Vaitkus <[email protected]>
Co-authored-by: Antanas Vaitkus <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
PR/major-edits
type/proposal
Proposal for addition/removal of features. May need broad discussion to reach consensus.
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.
During the OPTIMADE meeting in June 2021, we discussed in room 2 how the OPTIMADE standard could be expanded to allow the sharing of trajectory data. Based on the discussions with amongst others @giovannipizzi, @gmrigna, Adam Hospital, Tristan Bereau, Amit Gupta, Corey Oses, Ellad Tadmor, Maithilee Motlag, and Daniel S Karls, I have written a first draft for adding a trajectory endpoint. This will hopefully be a good base for further discussion.
The PR adds a trajectories section (in this PR section 7.3), that defines how a client can query and retrieve data from trajectories and how the server can share this data. We have tried to do this in a general way so that many different kinds of trajectories can be shared.