Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
W
WindEnergyToolbox
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
toolbox
WindEnergyToolbox
Merge requests
!9
adding generate-spreadsheet.md
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
adding generate-spreadsheet.md
tlbl/WindEnergyToolbox:master
into
master
Overview
0
Commits
5
Pipelines
0
Changes
2
Merged
tlbl
requested to merge
tlbl/WindEnergyToolbox:master
into
master
8 years ago
Overview
0
Commits
5
Pipelines
0
Changes
2
Expand
0
0
Merge request reports
Viewing commit
5e21ac9b
Prev
Next
Show latest version
2 files
+
139
−
56
Inline
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
Files
2
Search (e.g. *.vue) (Ctrl+P)
5e21ac9b
Merge remote-tracking branch 'upstream/master'
· 5e21ac9b
tlbl
authored
8 years ago
docs/houserules-mimerhawc2sim.md
0 → 100644
+
83
−
0
Options
House Rules for ```mimer/hawc2sim```
====================================
Objectives
----------
*
Re-use turbulence boxes (save disk space)
*
Find each others simulations, review, re-run
*
Find working examples of simulations, DLB's
*
Avoid running
House rules
-----------
*
New Turbine model folder when a new size of the turbulence box is required
(so basically when the rotor size is different)
*
One set ID refers to one analysis, and it might contain more than one DLB
*
If you realize more cases have to be included, just add them in the same
set ID. Don't start new set ID numbers.
*
Log file
*
Indicate which DLB used for the given "set ID" in the log file
*
Indicate the changes wrt to a pervious set ID
*
Write clear log messages so others can understand what is going on
*
Indicate in the log if something works or not.
*
Indicate if a certain set ID is used for a certain publication or report
*
Keep a log file of the different letters
*
Disk usage quota review
*
When results are outdated or wrong, delete the log and result files, but keep
the htc, data and pbs input files so the set ID could be run again in the
future. This is especially important if the given set ID has been used in a
publication, report or Master/PhD thesis.
HAWC2 folder structure
----------------------
The current DLB setup assumes the following HAWC2 model folder structure:
```
|-- control
| |-- ...
|-- data
| |-- ...
|-- htc
| |-- DLCs
| | |-- dlc12_iec61400-1ed3.xlsx
| | |-- dlc13_iec61400-1ed3.xlsx
| | |-- ...
| |-- _master
| | `-- dtu10mw_master_C0013.htc
```
The load case definitions should be placed in Excel spreadsheets with a
```
*.xlsx``` extension. The above example shows one possible scenario whereby
all the load case definitions are placed in ```htc/DLCs``` (all folder names
are case sensitive). Alternatively, one can also place the spreadsheets in
separate sub folders, for example:
```
|-- control
| |-- ...
|-- data
| |-- ...
|-- htc
| |-- dlc12_iec61400-1ed3
| | |-- dlc12_iec61400-1ed3.xlsx
| |-- dlc13_iec61400-1ed3
| | |-- dlc13_iec61400-1ed3.xlsx
```
In order to use this auto-configuration mode, there can only be one master file
in ```_master``` that contains ```_master_``` in its file name.
For the NREL5MW and the DTU10MW HAWC2 models, you can find their respective
master files and DLC definition spreadsheet files on Mimer. When connected
to Gorm over SSH/PuTTY, you will find these files at:
```
/mnt/mimer/hawc2sim # (when on Gorm)
```
Loading