Joerg Henrichs

I have been thinking of some kind of ... tracing library. E.g. a runtime call-graph creation (which then could be used to visualise data dependency, e.g. you see data going...

As mentioned in the telco last night: I might be able to get a student to work on PSyclone for around 10 weeks. Given that it might require some initial...

> A lightweight debugging/profiling version of PSyData would be good - #2186. i.e. an automatic version of the most reliable and available debugging method aka `WRITE(*,*)`. Just printing the values...

> Thinking about @hiker's original point 5: "Creating unit tests for kernels? That might be reasonable easy with psyke(?)" In the adjoint test-harness generation we construct an algorithm that initialises...

LFric provides the api parameter (both the old Makefile one and FAB as well ... I just realised, I need to checkout the latest version after the split, but I...

> Creating a new branch which will modify the adjoint metadata appropriately. This branch will create a new `ArgOrdering` class which uses the new metadata to call methods representing arguments...

@arporter , I had to re-check that. While it is likely that I never tested the NAN library with the new build approach (just copying the source files into the...

Additional todo item: - [ ] Rename the PSyData modules to follow LFRic naming conventions.

Issue is that `floor` is not supported in PSyIR (it ends up as a code block). Three changes required: 1. ``` --- a/src/psyclone/psyir/frontend/fparser2.py +++ b/src/psyclone/psyir/frontend/fparser2.py @@ -962,6 +962,7 @@ class...

This is mostly a duplicate of #1990, but it mentions the problem of protected attributes :( Potential solution could be to require explicit setter functions to be implemented (e.g. for...