Chris Krenn

Ok, I'll take a look at _StepRecord and ExecutionGraph when I can.

Hi Jeremy, (cc: @FrankD412) Thanks very much for reviewing this request. I'll try to respond point by point... Can you expand on the use case for this a little more?...

@FrankD412, @FrankD412, @jsemler, @daub1, Can you share your thoughts and plans about whether a conductor running a single maestro study will ever be parallelized? The simplest solution for storing indices...

A closely related request would be to include job ids in "maestro status"

Hello Frank, I’d like multiple instances of code.py to run in parallel in different directories. -Chris Chris Krenn Lawrence Livermore National Laboratory [email protected] 925-423-8636 From: Francesco Di Natale Reply-To: LLNL/maestrowf...

I agree that $(OUTPUT_PATH) is unnecessarily confusing. I would propose that $(OUTPUT_PATH_ROOT) point to the root directory and $(OUTPUT_PATH) point to the run directory.

We had a brief conversation about this today. Currently `$(OUTPUT_PATH)` in `study.yaml/env/variables` points to the directory in which timestamped directories are created, but `$(OUTPUT_PATH)` in `cmd` blocks points to the...

@FrankD412, (cc: @jsemler) Would you consider a pull request that enabled the user to define the directory structure? The default would be "{{output_path}}/{{prefix}}_{{year}}{{month}}{{day}}-{{hour}}{{minute}}{{second}}/{{step}}/{{instance}}", and this would reproduce your current naming...

Hello Frank, @dinatale2 Are all study steps stored in a flat directory structure? That's what the code seems to suggest, but I am not completely sure. (I am starting the...

I did notice the reservation entry. It is my understanding that qos=exempt lets you break some limits like active jobs per user or active nodes per user when using a...