Add optional configurable cloud_level parameter (related to #65)#68
Open
AlexPGroot wants to merge 4 commits into
Open
Add optional configurable cloud_level parameter (related to #65)#68AlexPGroot wants to merge 4 commits into
AlexPGroot wants to merge 4 commits into
Conversation
…ngleton, as that is how pagoo operates originally
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.
Add optional configurable cloud_level parameter (related to #65)
This pull request adds a
cloud_leveltoPgR6.R, allowing for the user to have more control over what is considered the cloud genome:.cloud_levelto private.$cloud_levelto public, which is by default set to"singleton"to keep functionality as originally intended.$cloud_levelby usingpg$cloud_level <- ("singleton"|"single"|"s")or numeric value such as15core_genesis calculated.