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
Even though all of these fields are available in mpr.tasks.available_fields however the REST API also do not have values for these fields at the /materials/tasks endpoint, but at the /material/core endpoint for material ID (mp-1187313) returns:
While these fields are part of available_fields and were requested, they are not present in the raw task doc returned from the database, so they get "lumped" in with fields_not_requested. Technically, they're simply "unset" but that distinction is not made when fields_not_requested is set by mp-api.
I've made a note in 87c072e and will try to come up with a fix when I get the chance. HTH.
Code snippet
What happened?
Running:
task_doc.fields_not_requested
Returns:
Even though all of these fields are available in
mpr.tasks.available_fields
however the REST API also do not have values for these fields at the /materials/tasks endpoint, but at the /material/core endpoint for material ID (mp-1187313) returns:I realize that the tasks endpoint does not have the data but the other endpoint does, should the data be harmonized with the MP API?
Version
mp_api: '0.42.2', pymatgen: '2024.9.17.1', emmet: '0.82.2'
Which OS?
Log output
The text was updated successfully, but these errors were encountered: