Imputation_beagle_tutorial
nsd
| Imputation_beagle_tutorial | nsd | |
|---|---|---|
| 1 | 8 | |
| 26 | 4 | |
| - | - | |
| 0.0 | 4.7 | |
| about 2 years ago | 6 months ago | |
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Imputation_beagle_tutorial
-
Beagle Imputation Tips?
I found this tutorial, which may be quite out of date, and which says to impute once per chromosome: https://github.com/adrianodemarino/Imputation_beagle_tutorial
nsd
-
Announcing Hush, a modern shell scripting language
Repository of scripts written in the language - https://github.com/ngs-lang/nsd
-
Bash functions are better than I thought
> there isn't really an entry point in murex scripts
I have a nice trick in NGS for that. Under the idea that "small scripts should not suffer", script is running top to bottom without "entry point". However, if the script has defined main() function, it is invoked (with command line arguments passed).
Example - https://github.com/ngs-lang/nsd/blob/afe0cad5e506ec4ee2fa924...
> `args` still contains more boilerplate code than I'm happy with
Is there anything preventing you to have exactly the same functionality but with syntactic sugar that it looks like parameters declaration? (Just to be clear, keeping all the ARGV machinery).
Something like (assuming local variables are supported; if not, it could still be $args[Flags] etc):
function hippo(name:str, hungry:bool) { -
I love jq, I hate jq. Help a competent grepper get a grasp on the terse language!
NGS Scripts Dumpster - collection of small scripts in NGS
- GitHub – nushell/nushell: A new type of shell
-
No, you can't do it better in Python or bash (challenge)
Doing DevOps today? 99% either abuse bash or abuse a general purpose programming language.
bash does not meet any modern expectations from a programming language: syntax, error handling, data structures
General purpose languages such as Python, Ruby, etc are not domain specific enough to have the desired facilities.
Here is small example of straightforward solution to a small problem: list all CloudFormation stacks that are managed by the given CodePipeline.
https://github.com/ngs-lang/nsd/blob/02d66abb844b7dd6077b9976e3a03659cf4b3660/aws/codepipeline/pipeline-stacks.ngs
- Which CloudFormation stacks are managed by a CodePipeline - script
-
Delete CloudFormation Stack Including S3 Objects
The script is at https://github.com/ngs-lang/nsd/blob/master/aws/cloudformation/delete-stack.ngs
- What is your favorite shell and why
What are some alternatives?
fastp - An ultra-fast all-in-one FASTQ preprocessor (QC/adapters/trimming/filtering/splitting/merging...)
ngs - Next Generation Shell (NGS)
bash-core - Core functions for any Bash program.
oh - A new Unix shell.
fx - Terminal JSON viewer & processor
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
nushell - A new type of shell
basalt - The rock-solid Bash package manager.
pass-import - A pass extension for importing data from most existing password managers
homebrew-core - 🍻 Default formulae for the missing package manager for macOS (or Linux)
nvim-jqx - Populate the quickfix with json entries
oil - Oils is our upgrade path from bash to a better language and runtime. It's also for Python and JavaScript users who avoid shell!