Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
X
xBOUT-examples
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
David Bold
xBOUT-examples
Commits
6b9db738
Commit
6b9db738
authored
4 years ago
by
John Omotani
Browse files
Options
Downloads
Patches
Plain Diff
Contributor guidelines
parent
f9f75910
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+32
-1
32 additions, 1 deletion
README.md
with
32 additions
and
1 deletion
README.md
+
32
−
1
View file @
6b9db738
xBOUT examples
==============
A set of self-contained examples showing various features of
[
`xBOUT`
](
github.com/boutproject/xBOUT
)
.
A set of self-contained examples showing various features of
[
`xBOUT`
](
github.com/boutproject/xBOUT
)
.
Contributor guidelines
----------------------
In order to make the examples easy to use, we keep them in a single repo and do
not use git-lfs. That means we need to stop the repo from getting too big. We
also want the examples to be self-contained, so people do not need to have
BOUT++ set up and running before they can run these examples.
Some guidelines for making examples:
*
Ideally the code and inputs to create datasets should be publically available
and linked from the example.
*
Even if the code is available, the dataset needed for each example should be
archived on
[
Zenodo
](
zenodo.org
)
so that the example can be run
independently.
* Please provide a setup call to download the data from Zenodo if it is not
present.
*
We will use squash-merging of pull requests to minimise the number of data
objects (e.g. plot output in Jupyter notebooks) present in the history.
* We should also try to make PRs with significant changes as complete as
possible before merging so that we minimise the number of PRs that make
changes to data objects.
* Small PRs fixing typos, etc., should be fine as long as they do not
modify data.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment