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

What are plans for this repo? #1

Closed
StephenGriffies opened this issue Oct 26, 2018 · 6 comments
Closed

What are plans for this repo? #1

StephenGriffies opened this issue Oct 26, 2018 · 6 comments

Comments

@StephenGriffies
Copy link

Looks like this repo has been idle since November 2017. What are the plans? Its description is confusing since users might think there are no example test cases for MOM5, whereas there are many under the MOM5 repo.

@navidcy
Copy link

navidcy commented Nov 17, 2021

Let's delete the repo? I got actually confused by it.

However, me and @dhruvbhagtani were looking for the examples in the MOM5 repo and couldn't locate them. We could only find pdf files describing the examples but nowhere the actual source files of the examples are to be found. Are we missing anything? We were hoping to see some ocean-only examples somewhere...

@aidanheerdegen
Copy link
Contributor

Related issue

COSIMA/access-om2#42

@aidanheerdegen
Copy link
Contributor

See also

mom-ocean/MOM5#197

@aidanheerdegen
Copy link
Contributor

There is an issue with some of the test cases having large binary inputs, but at least the configuration files could be stored here.

Smaller cases can be stored in their entirety. For example I have added the bowl1 case

#2

I intend to use this in the MOM5 CI testing, so it made sense to add it here.

@aidanheerdegen
Copy link
Contributor

I have kept the bowl1 branch, as it occurred to me could use this as a strategy to keep all configs in a single repo, but be able to check out individual configurations. If all updates to a config are pushed to the branch with that config name, and then merged, then it should be possible to check out only that branch to select a single configuration.

@aidanheerdegen
Copy link
Contributor

I've added six of the smaller examples in total. I'll close this issue, and if there is demand for some of the larger examples we can look into solutions for large binaries, e.g. git annex or Git LFS

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

No branches or pull requests

3 participants