Skip to content

Comments

Lucas' RVE data schema#11

Open
arachid1 wants to merge 24 commits intomainfrom
20250807
Open

Lucas' RVE data schema#11
arachid1 wants to merge 24 commits intomainfrom
20250807

Conversation

@arachid1
Copy link
Collaborator

@arachid1 arachid1 commented Aug 7, 2025

Use this notebook to extract and understand content from the various files expected under each Case_XX folder:
📎 https://github.com/openmsi/misc_scripts/blob/main/populate_rve_schema.ipynb

TODOs

Verify the structure of all, but especially:

  • BC_Dirichlet.inp (boundary conditions)
  • BC_Macro_Uniaxial.inp (macroscopic loading configuration)

Double-check units
Refine and confirm field descriptions
Decide which fields should be required vs optional

Notes

It’s not clear if the files under loading/inputFiles/ in a given Case_XX folder represent a single experiment, since some of them also appear in folders like loading/analysis_{DATE}. If these represent multiple experiments, we may need to allow lists of file uploads for those cases. Similarly, this applies to extraction logic for files under that folder, like materialProperties.inp.

We need to determine:

  1. Which files are always present and should therefore be mandatory
  2. Whether we should support a generic upload field for any additional or less common files

Some files (e.g. materialProperties.inp) contain a lot of detailed data and might be better treated as raw file uploads, rather than trying to parse and map all their contents into fields.

@arachid1
Copy link
Collaborator Author

arachid1 commented Oct 13, 2025

script that creates entries:

https://github.com/openmsi/misc_scripts/blob/main/RVE/create_and_fill_form.ipynb

  • file uploads fields (e.g., Lath properties file) still show the dropdown with data type on the portal, and I'm not sure why. I think I defined the names properly.
  • fields that are missing just don't show. Maybe I should add 'required=[...]'.
  • I created the entries, but when the following return 0:
entries = client.get("entry", parameters={"query": "^Case_", "limit": 1000})
print(len(raw_data))

@Xarthisius
Copy link
Contributor

I think we've been through this on a separate form (laser shock perhaps? can't find my comment). In my personal opinion, having long, complicated property names full of spaces and special characters is a no-go. You go to extremes here, e.g.:

                "Standard deviation of aspect ratio B to A": {
                    "type": "number",
                    "description": "Spread of B/A aspect ratio",
                    "propertyOrder": 4
                },

where property name is actually longer than its description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants