plans using peak stats fail in print summary

[ambarb]

add flow control to assign the key a number if it does not have one. this affects alignment of m1 and m3 (m3_check() and the align generator in the profile.)

[awalter-bnl]

@ambarb I am not sure I understand what you want here, any suggestions? Let me know when is a good time to stop by and look at the growing list of issues at SIX (preferably with @bisogni or yourself present). Feel free to put something on my calender, I think you have mentioned that you would like to wait until after Tuesday but I can come earlier if you prefer.

[ambarb]

This is also related to
bluesky/bluesky#1017

I am not sure if this work proceeding in the above will be something that rolls out soon.

And in general the discussion found here applies.
bluesky/bluesky#1075

[ambarb]

let me talk with @bisogni and we will set up a time.

[mrakitin]

That is a high priority issue to be resolved (according to @bisogni).

[ambarb]

For the m3 alignment? Or the larger problem of peaks not playing nice with print_summary

[mrakitin]

I think it's for the larger problem.

[ambarb]

I have one or two issue reports in Bluesky about this. I think the others have suggested that we make plans that are more defensive rather than enabling this feature in Bluesky, which would deliver a functionality that spec has.

bluesky/bluesky#1017