BUMPS-WEBVIEW(1)
π BUMPS-WEBVIEW(1) π
okay so bestie, welcome to the bumps-webview man page β it lives in the User Commands section of the manual, and it's literally the webview interface situation for Bumps. buckle up π
β¨ NAME β¨
bumps-webview β a webview interface for Bumps π¦
πΈ DESCRIPTION πΈ
the vibe is: you get a whole webview interface for Bumps. here's the usage, exactly as it comes, no cap:
usage: bumps-webview [-h] [-x] [--external] [-p PORT] [--hub HUB]
[--fit {dream,scipy.leastsq,amoeba,de,lm,newton}]
[--start] [--store STORE] [--read_store READ_STORE]
[--write_store WRITE_STORE] [--exit] [--serializer
{pickle,dill,dataclass}] [--trace] [--parallel PARALLEL] [--path
PATH] [--no_auto_history] [--convergence_heartbeat]
[--use_persistent_path] [filename]
π§ positional arguments π§
filenameβ the problem file to load, and it's gotta be either a.pyor a.json(serialized)fitproblem. that's the whole assignment bestie π
π options π
-h,--helpβ shows this help message and then dips out. classic. π-x,--headlessβ do NOT automatically load the client in the browser. it's giving invisible mode π--externalβ listen on all interfaces, including external ones. if you don't set this flag, it's local connections only, periodt π-p,--port PORTβ the port on which to start the server. pick your number, queen π’--hub HUBβ api address of the parent hub. this one is only used when it's called as a subprocess, iykyk π°οΈ--fit {dream,scipy.leastsq,amoeba,de,lm,newton}β the fitting engine you wanna use. check the manual for the deets on each one π₯--startβ start the fit the moment the problem is loaded. no waiting around π--store STOREβ setsread_storeandwrite_storeto the same file, one flag two jobs β¨--read_store READ_STOREβ read the initial session state from a file. heads up: this overrides--storeπ--write_store WRITE_STOREβ output file for the session state. also overrides--storeπ--exitβ end the process when the fit is complete. β οΈ but fr fr, fit results are lost unlesswrite_storeis specified. protect your data bestie π--serializer {pickle,dill,dataclass}β the strategy for serializing the problem. if the store already has a value defined, it'll use that one instead π«--traceβ enable memory tracing. it prints after every uncertainty update indreamπ§--parallel PARALLELβ run the fit using multiprocessing for parallelism. pro tip: use--parallel=0for all cpus, all of them, every single one π--path PATHβ set the initial path for the save and load dialogs ποΈ--no_auto_historyβ disable auto-appending problem state to history on load and at fit end. the history girlies are gonna be devastated π--convergence_heartbeatβ enable the convergence heartbeat for the jupyter kernel. it keeps the kernel alive during the fit, like a little life support π«Ά--use_persistent_pathβ save the most recently used path to disk so it persists between sessions. memory of a goldfish, but make it β¨persistentβ¨ πΎ
π¦ SEE ALSO π¦
the full documentation for bumps-webview is maintained as a Texinfo manual. if the info and bumps-webview programs are properly installed at your site, then this command:
info bumps
should give you access to the complete manual. go read it, it's iconic π
and that's the whole page bestie!! this was BUMPS, February 2025, signing off ππ
β¨ stay slay, stay serialized, and always specify your write_store π
π¦ where this page comes from
- debian trixie: python3-bumps 1.0.0b2-2 Β· LicenseRef-public-domain
- ubuntu questing: python3-bumps 1.0.0b2-2
- ubuntu resolute: python3-bumps 1.0.3-3 Β· LicenseRef-public-domain
- ubuntu stonking: python3-bumps 1.0.5-1 Β· LicenseRef-public-domain
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms