Tyler Mathis

Okay, got it. For 1., I am going to take a pretty hard stance against allowing users to inject arbitrary data into MP's base task doc. I would rather lean...

On MP's side, we are trying 1) to standardize our schema and 2) transition to using TaskDoc for everything. Including updating the schema for the existing tasks collection on MP...

Good to know. Color schemes came up in a MP update call a few weeks ago in a related context, I can bring it up again in the next call...

@tschaume , is this still relevant?

@tschaume, the results here are reproducible. This is a side effect of user group access control behavior mixing with bulk download behavior in the client. I'll link you my slack...

@mkhorton, running incremental builds caused some of the materials that would have been binned in the GNoME dataset to get the default "BY-C" license in the `builder_meta`, I've fixed all...

Would still require running a query with the client I think -> get the GNoME material ids doing something similar to what I pasted above, just include `material_id` in the...

closing due to no movement upstream and no current impact on emmet users. can re-evaluate in the future if needed

the `get_entries_by_chemsys` function only pulls `GGA_GGA+U` entries by default, try: `entries = mpr.get_entries_in_chemsys(["C", "O", "Yb"], additional_criteria={"thermo_types": ["GGA_GGA+U", "R2SCAN"]})` using your same print loop: ```python Retrieving ThermoDoc documents: 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████| 157/157 [00:00>...

We can clarify that that is the default behavior in the function signature. @tschaume, I dug a bit and found where defaulting to `GGA_GGA+U` entries only got obfuscated. We can...