101 tutorials

[FlorianDeconinck]

Adding 101 tutorials for the stack & the common workflows

• NDSL
  • Pure gt4py
  • NDSL
• Fortran porting (serialization)

[FlorianDeconinck]

This is looking good.

Overall I'd like to rename the folder "gt4py" -> "NDSL" and "serialbox" -> "Porting Fortan".

I also think we need to be careful about exposing a lot of the gt4py entrails that are covered by NDSL API. While we, the SMT team, require to know about it, the end users shouldn't. As well let's rename OO_gt4py to NDSL_basics because it factually is how we use GT4Py in NDSL.

[FlorianDeconinck]

• Describe GT4Py as a stencil system to differentiate with the full program optimizer later
• Remove gt4py.storage since we are already using ndsl.FloatField lets remove that distinction and use Quantity directly. Allocation are common scare for scientists, lets have a single point of entry
• Add the main stencil restriction: write with offset in IJ, demonstrate a failure
• Add compile time switch (__INLINED)

[gmao-ckung]

Quick question: where do I add the compile time switch (__INLINED)?

[FlorianDeconinck]

Look at this unit test in gt4py

__INLINED is a conditional switch, where the condition has to be given in the externals. It turns the conditional into a compile time conditional (e.g. the externals can't change at runtime) and does branch culling so the conditional is removed from the runtime

[gmao-ckung]

I addressed most of the bullet points. I'm still not sure what (__INLINED) is supposed to help with.