Configure SWIM Setup
-
(New Jul25 - but still developing)
- ?theme = ocean (or draft, wood, black, etc.)
- ?focus = emit (or socio, carbon, resp etc.) - which package has focus -> more plots and params visible
- ?soc : only demography, economy, energy: -> more space and faster, for exploring only beginning of chain
- ?noinfo : hide ⓘ info (same as button)
- ?fast -> loads code compiled with fastLinkJS (slower but better for debugging)
- ?wasm -> loads code compiled to WASM instead of JS - more info next page
- ?conso : open console automatically (useful to check progress / debugging)
- ?test -> test output -> console
- ?help -> list options -> console
- Preset the value of any model parameter using the format Scimod@param=value
- * Scimod is the name of the class in the code - e.g. Demog, ElecSupply, EmitAtmo, Carboncycle... - (*sometimes* same as on cog)
- * param is the name in quotes after eg VParam("myname", ...) - (likely same as by displayed) - replace spaces by _ or %20
- So to find the names, you may need to check the code - first press 'Code' button, then select a cog to open its code.
- For example: EmitAtmo@choose_path=Pledges_LTS
- (sorry some labels confusing - to fix with doc later)
- Combine options with &
- Example: ?focus=energy&theme=wood&noinfo&ElecSupply@Region_to_plot=China
- Example: ?conso&focus=resp&theme=ocean&EmitAtmo@choose_path=Pledges_LTS
- The same parameters can be specified from command line as --args
- Setup for Plot arrangement, Scales etc., Layout
- Demo scripts (sequence of setups... )
- Save your current setup, reload others
Although the main way to adjust parameters is by pulling visual controls (see prev page) it can be useful to open SWIM with a specific setup, by adding 'query' parameters to the end of the URL
General Setup:
Model Parameters:
Combinations:
For JVM-Desktop / Scala-Native versions:
Not yet working in SWIM, to revive soon:
(functions which were in former JCM - as JVM-desktop version)
This is a first step towards a common setup / scripts system spanning the web-app, desktop, and native platforms. Eventually, this should enable running custom setups and demos to illustrate a specifc point (e.g for teaching students), but also more systematic analyses. So the web-app is good for exploring new ideas visually, then the JVM or Native versions can run the same science code faster, as for probabilistic analyses integrating over thousands of model runs.
Next: History
(Overview)