Original setup of repository, with licences, .gitignore and Commons directory (master branch)#1
Open
jmpetit wants to merge 2 commits intoOSSOS:masterfrom
Open
Original setup of repository, with licences, .gitignore and Commons directory (master branch)#1jmpetit wants to merge 2 commits intoOSSOS:masterfrom
jmpetit wants to merge 2 commits intoOSSOS:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the original setup of the OSSOS_Models repository. I've created a rough README.md file, added the licence files and .gitignore. I also added the Commons directory, which contains the libraries and programs that are common to each model.As of today, 2026-02-25, this contains only Fortran95 source codes and related files. All this is done in master branch.
In the future, we plan to add more directories, one for each population - Classical, Detached, DIstant_resonances, Inner, Plutinos, Scattering, Twotinos - which will be edited each in its own branch, with same name.
The fact that there is a Commons directory makes the use of differnt branches a little more complexe I guess. I've created the Commons directory in a state that is already suitable to generate the Classical and Inner models (tested them already). Then for each new population , I'll create a branch in which I will create directory . It will inherit the content of directory Commons as it stands at the time. In the process of creating the model for , I may have to add some routines to the Commons libraries. If so, I'll need to merge branch into branch master so a future other Population/branch/directory will inherit the extended Commons.
JJ, does that seems correct to you ?