Using figure_of_merit_context with multiple lines of output

[amklinv-nnl]

Discussed in https://github.com/GoogleCloudPlatform/ramble/discussions/307

^{Originally posted by **amklinv-nnl** November 3, 2023} I am trying to add a new package for SNAP and am grateful for the help y'all have provided so far. I am now able to successfully run my benchmark, but I'm struggling to capture the output in the way I'd like. I ran HPL and `ramble workspace analyze` produced the following output ``` From Workspace: hpl_test (hash: 717093d6d735577adab4292ad1456ab22648cccce537b1dccc084836e6b89d13) Experiment hpl.standard.arbitrary_name figures of merit: Status = SUCCESS N-NB-P-Q = 500-192-2-2 figures of merit: Time = 0.00 s GFlops = 2.5272e+01 GFLOP/s N-NB-P-Q = 500-384-2-2 figures of merit: Time = 0.01 s GFlops = 1.3972e+01 GFLOP/s N-NB-P-Q = 1000-192-2-2 figures of merit: Time = 0.01 s GFlops = 6.4734e+01 GFLOP/s N-NB-P-Q = 1000-384-2-2 figures of merit: Time = 0.02 s GFlops = 3.7973e+01 GFLOP/s N-NB-P-Q = 500-192-1-4 figures of merit: Time = 0.00 s GFlops = 2.8448e+01 GFLOP/s N-NB-P-Q = 500-384-1-4 figures of merit: Time = 0.00 s GFlops = 1.9191e+01 GFLOP/s N-NB-P-Q = 1000-192-1-4 figures of merit: Time = 0.01 s GFlops = 6.9491e+01 GFLOP/s N-NB-P-Q = 1000-384-1-4 figures of merit: Time = 0.02 s GFlops = 3.8291e+01 GFLOP/s N-NB-P-Q = 500-192-4-1 figures of merit: Time = 0.00 s GFlops = 1.9776e+01 GFLOP/s N-NB-P-Q = 500-384-4-1 figures of merit: Time = 0.01 s GFlops = 1.2417e+01 GFLOP/s N-NB-P-Q = 1000-192-4-1 figures of merit: Time = 0.01 s GFlops = 4.8506e+01 GFLOP/s N-NB-P-Q = 1000-384-4-1 figures of merit: Time = 0.02 s GFlops = 2.7993e+01 GFLOP/s ``` I would like to do something similar for SNAP, but the process grid unfortunately is output over multiple lines. ``` Parallelization Parameters npey = 4 npez = 4 nthreads = 2 ``` This may just be a regular expression issue, but I can't for the life of me figure out how to capture that info for figure_of_merit_context. Can you please provide guidance?

[rfbgo]

Closing due to lack of activity. Please feel free to reopen, or continue the discussion over in #307