Skip to content
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] Wide vs long tables? #43

Open
kelle opened this issue May 7, 2024 · 2 comments
Open

[Discussion] Wide vs long tables? #43

kelle opened this issue May 7, 2024 · 2 comments
Labels
question/discussion Further information is requested

Comments

@kelle
Copy link
Contributor

kelle commented May 7, 2024

Folks recently requested that parameters like v_sin_i, rotation_rate, and inclination be added to SIMPLE. This got me thinking about...should these be three separate new wide tables? or new parameters in the long ModeledParameters table? Or parameters in a new MeasuredParameters table? How do we decide if something should be in a wide vs long table? I have a sense in my head about how/why we should encourage folks to distinguish between "measured" and "modeled" parameters, but where/how do we draw the lines between those two different types of getting at underlying physical parameters?

@arjunsavel
Copy link
Collaborator

Yeah, this is tricky. I feel like I have a gut instinct for what's "measured" and what's "modeled," but upon digging into those measurements, a lot seem modeled...

@kelle
Copy link
Contributor Author

kelle commented May 7, 2024

draft: "primary" parameters are in wide tables while "secondary" parameters are in long tables. What primary and secondary mean is case dependent.

I think we can have examples/implementations of both in the template and folks can decide for themselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question/discussion Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants