OpenBUGS(1)
π OpenBUGS
okay bestie, so this is the section 1 manual page for OpenBUGS β like, the actual program, not some library situation. pull up a chair, we're doing this π«Ά
β¨ SYNOPSIS β¨
OpenBUGS [options] [args]
that's it. that's the whole vibe. options and args, in whatever order your heart desires π
πΈ EXAMPLES πΈ
okay these are literally the receipts, bestie β copy them exactly, no cap:
OpenBUGS
OpenBUGS script.txt
OpenBUGS script.txt > res.lst
OpenBUGS < script.txt >res.lst
OpenBUGS -t script.txt
env BUGSIN="/dif/dir" BUGSOUT="/other/dir" OpenBUGS script.txt >
/path/to/res.lst
see how the last one sets env vars right there on the same line? iconic. that's the env function doing its lil thing β¨
π¦ DESCRIPTION π¦
so what you do is you invoke OpenBUGS β usually you're handing it a script β and it does template expansion inside that script file to sort out your directory paths. it's giving helpful, honestly π
here's the tea: any name sitting inside curly brackets in a script file gets read as an environmental variable, and then the value of that variable gets substituted in. so like, bracket name in, value out, slay π
you can set those environmental variables a few ways:
- temporarily, on the same command line as the OpenBUGS execution, using the
envfunction - on a separate line
- or in a default startup file
β οΈ heads up bestie: there's now a way easier option β the OpenBUGS script command modelSetWD('path') sets the path where OpenBUGS looks for model, data and initial value files. so much less drama. but the environment variable mechanism is still available for backward compatibility, so old scripts don't get left on read π
π OPTIONS π
-dβ dry run, bestie. the script just gets printed onstdoutso you can see what would happen without actually committing. vibe check before the commit, ykwim? π-bβ specify the number of curly brackets used to delimit template names. yes, the curly bracket count is configurable. we love a customizable delimiter π-hβ help. the classic. when in doubt,-hit out π«Ά-tβ do not perform template expansion. so those curly-bracket names just stay exactly as they are, no substituting, no nothing. periodt π₯
π SEE ALSO π
the main documentation for OpenBUGS ships as HTML pages, not as manpages (sorry, we know π). by default they're installed in /usr/local, and the top-level page β your main character entry point β is:
/usr/local/lib/OpenBUGS/doc/Manuals/Contents.html
go read it, it's literally the manual π
and that's the whole page, bestie!! β¨ this was Version 3.2.3, dated March 2014 β yeah, she's a vintage icon ππ¦ go forth and run your scripts, mwah π
π¦ where this page comes from
- nixos 26.05: OpenBUGS 3.2.3
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms