u-dales

u-dales copied to clipboard

Assign flow forcing in namoptions

3

This issue is to discuss how the flow forcing should be handled. There are several ways to force the flow. It would be good to have a separate section for...

bss116

Large static memory allocation on hpc system

10

**Describe the bug** Code will crash on one of the first lines of a subroutine where a static memory declaration over some threshold value is made. Only occuring when compiled...

tomgrylls

Currently only field variables are saved in the restart initd and inits files. If the time-averaged statistics variables are added, then the time-average of the statistics output will no longer...

bss116

Add ifort support in CI

1

Currently we only run CI tests with gfortran on macOS and Ubuntu. Ideally, since we also support ifort, we should also add the relevant tests using ifort to the CI...

dmey

madDipanjan

Sorry for the delay in getting this to you guys. I had some competing projects but didn't want this to get lost on my harddrive. This PR addresses the vast...

cc-a

Updated the example files and the namoptions documentation. Need to update the examples documentation. Closes #228

cedwardwilson

Update build instructions [depends on changes in T4]

1

mvreeuwijk

T1 Update user documentation

1

- [ ] #209 - [x] #192 - [ ] #210 - [ ] #213 - [ ] #214

mvreeuwijk

Use the [-std](https://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html#index-std_003dstd-option) option of gfortran to flag any non-standard compliant parts of the code and consider what would be required to adopt usage.

cc-a