forked from simwrapper/simwrapper
-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(dash): Project-level dashboards, vizes, and calculation topsheets
Create a folder named 'simwrapper' at any level relative to your current output folder (inclusive). All folders will inherit the YAML files from those folders. File paths in YAML are always interpret as if they are in the currently viewed folder, NOT the folder from which the YAML file is stored. Squashed commit of the following: commit d5cef22778b18b688e69ea53ea213c3172840eee Author: Billy Charlton <charlton@vsp.tu-berlin.de> Date: Thu Dec 16 11:13:15 2021 +0100 feat(dash): viz-* yaml files can now be in any simwrapper/ folder Just like dashboards and topsheets! commit ea428fe4f9eabca0a7ea1830ec6b7ba91e61b51e Author: Billy Charlton <charlton@vsp.tu-berlin.de> Date: Wed Dec 15 18:37:33 2021 +0100 Dashboards and topsheets can be in any nearby simwrapper/ folder Dashboard and topsheet YAML configurations can now be in the current folder OR in any simwrapper folder at any level in the tree hierarchy at this level or above. In other words, if you are looking at ~/data/berlin/myrun01, dashboards and topsheets will be found in that folder and also in: ~/simwrapper ~/data/simwrapper ~/data/berlin/simwrapper ~/data/berlin/myrun01/simwrapper Configuration files of the same name get superceded; the closest to the current folder take precedence; thus a project can have defaults but you can override them if you like. commit 63308fb4237a2d829305172b241c1e04ede63894 Author: Billy Charlton <charlton@vsp.tu-berlin.de> Date: Wed Dec 15 13:28:19 2021 +0100 cache & optimize directory fetching
- Loading branch information
Showing
21 changed files
with
297 additions
and
174 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.