Boilerplate code for fast deploy of NDSL

[FlorianDeconinck]

Description
In order to present an unified, easy and clean API to the user, we start here a series of "boilerplate" code that wrap common use cases. The first of those is the "quick test" with a one tile, no boundaries, no comms, for numpy and orchestrated dace:cpu

How Has This Been Tested?
Adding two boilerplate code

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• New check tests, if applicable, are included

[fmalatino]

lgtm

[xyuan]

would we have a util directory, and put all these utility code there instead of ndsl directory?

[FlorianDeconinck]

I personally don't like util directories as they become a dumping ground for everything and anything quickly (we use to have one we clean up with Frank). Each tools & features should be named with what they do

[xyuan]

sure, that makes sense, thanks

…

On Wed, May 15, 2024 at 9:54 AM Florian Deconinck ***@***.***> wrote: I personally don't like util directories as they become a dumping ground for everything and anything quickly (we use to have one we clean up with Frank). Each tools & features should be named with what they do — Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFCG2D7RP2G7YUOGCUK3Y3ZCNSKBAVCNFSM6AAAAABHWLWJDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJSGYYTAOBZGE> . You are receiving this because your review was requested.Message ID: ***@***.***>

[oelbert]

Looks good. Small suggestion if you want for names.

Is part of the thinking that we will end up making a similar function for gpu orchestrated backends and others?

[oelbert]

Great, thanks!