Joerg Henrichs

Spaces introduces into real constants

2

While working on #1883, I detected one failure: In the `tutorial/practicals/LFRic/building_code/1_simple_kernels/part2/solutions` there is a `-2.0_r_def` in , which turns up inside KernCallArgList as `- 2.0_r_def` - notice the additional space!...

Literals with precision cannot be used to create a Literal

2

Passing `1.0_r_def` as name to the Literal constructor aborts (since the string does not match the regular expression). ``` _real_value = r'^[+-]?[0-9]+(\.[0-9]*)?([eE][+-]?[0-9]+)?$' ``` For now I remove `_r_def` at the...

While working on #1883, variable declarations were added to `KernCallArgList`. Unfortunately, there are many overlap between this class and classes in `dynamo0p3` (esp. the `DynCollection` based classes, which declare many...

Several variables in declared in `kern_call_arg_list` (of #1883) missed a pointer attribute. Either add support the pointer attribute, or use an applicable work around (see psy_data_node). This todo is mostly...

In order to create a proper extraction driver for LFRic, (#1483) we need to have the full PSyIR expression for all actual (implicit) kernel arguments. ATM this class only returns...

Temporary LFRic fixes for kernel driver creation

1

While working on #1483 , several work arounds need to be applied, because the PSyIR infrastructure is not fully implemented in LFRic. This ticket is used to document these temporary...

Field vector and array of fields and psy_data

6

@christophermaynard raised the issue about handling of array of fields. This issue is just to keep track of notes while extending the example. First of all, psydata handles array of...

Avoid compiling infrastructure for each process in pytest compilation tests

2

ATM, each processes in a (xdist-parallel) `pytest --compile` job compiles its own infrastructure (since we considered it dangerous if each process calls 'make' in the same tree, we could potentially...

ATM the output of the dependency creation tool does not support the output of subdirectories, e.g.: ``` $ cd fparser/example $ ./create_dependencies.py test_files/* $ cd test_files/ $ ../create_dependencies.py * b.o:...

While I was trying to use the dependency creation tool of fparser (in examples), I realised that if there should be an error in a Fortan file, the whole program...