-
Notifications
You must be signed in to change notification settings - Fork 1
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
Discussion on data structure #1
Comments
We could also have a look at this repo https://github.com/JuliaRheology/RHEOS.jl It'd be nice if we make the flow from our database to their fitting library easy. |
other cool software to check : https://reptate.readthedocs.io/ |
example of an organization of data shared for everyone on GitHub https://github.com/fivethirtyeight/data they stick to the CSV side of the force |
Nomenclature of the Society of Rheology |
Unique identifiers for samples to investigate https://github.com/IGSN |
Mix SQL and JSON files https://gitlab.obspm.fr/exoplanet/py-linq-sql/-/tree/main --> Sqlite has a json extension |
Opening this issue to discuss data structure:
Scope:
proposing a standard way to store and retrieve data
Proposing a dictionary of pandas dataframes as a good way to handle data from our primary sources:
When the order in the dictionary is meaningful, as for example in the rheology measurement case for which the steps order is important I propose to prepend an index to the step name
This structure is very generic and can be stored as a sqllite file very easily:
once you have the sqllite file you can explore it with for example:
The data can be read back into a dictionary of tables:
The text was updated successfully, but these errors were encountered: