Joerg Henrichs
Joerg Henrichs
Move the LFRic infrastructure files into subdirectories that are used in LFRic. This makes it easier to replace the included infrastructure with original LFRic files. This code removed the list...
#1742 shows that in some cases for example the variables used in defining the loop boundaries should not be included in the list of 'read' variables (`size(some_array,1)` - does not...
This is the stand-alone extraction library. Note that I have not added compilation tests (which we can do) to keep the patch smaller.
ATM the dependencies for the included LFRic infrastructure files is hardcoded. Once we update to use the latest fparser, we can automatically create this file using `$(FPARSER_ROOT)/example/create_dependencies.py ``` cd .../infrastructure...
Some tutorials appear to be outdated. In at least one case the solution file was fixed, but not the file the user is supposed to modify. Example: ``` psyclone/tutorial/practicals/LFRic/building_code/3_time_evolution$ diff...
We need simple, stand-alone dummy libraries for gocean API and for LFRic, so we can add compilation tests (which need a mod file): - [ ] Add dummy PSyData library...
For compilation tests (and when migrating to really new platforms) it is useful to have an extraction and reading library that does not depend on NetCDF. - [x] Implement basic...
While debugging various LFRic crashes, we found ourselves often in the position that we know a variable has incorrect values (not necessarily NAN, but e.g.0, or just garbage), and we...
ATM it is rather complicated to apply a psydata library with lfric. For example for nan testing: 1. Modify the psyclone transformation to apply a psydata transformation. 2. In the...
The directory layout of the internal infrastructure library and the LFRic infrastructure library is inconsistent, e.g. LFRic uses `field/field_mod.o`, `mesh/mesh.o` (and same for .mod files). Our copy of the infrastructure...