Firstly, thanks for trying it out, Andy! Very much appreciated!
Would it be possible to add in a hover to the Extracts Generators->Data->* ?
Indeed. Reported here
Also, for the Extracts Generators->Data->* it seems like it’s a bit inconsistent to me that, for example, it lists VTI, but is actually a pvti output.
Good point. I wonder if we should really not burden the user with which flavor of writer to use, instead have single entry for VTK-XML (or something more readable) and then create the *.vt??? variant based on the input dataset type. Thoughts?
Not a bad idea to just say Parallel VTK XML output and create the .pvt? variant, if it can be done in a non-confusing way. We’ve been doing it for so long though with .pvti, .pvtu, .vtm, etc. though that maybe we’ve trained the users too much in that way of thinking. I’ll leave it up to you though.
For the example it would be nice to have something written to disk as well.
Sure thing. I’m assuming you’re referring to the examples here. Reported here.
Yes – thanks!
When using the -c to change the registrationName for the channel, it keeps that name throughout and when writing out a file to disk it uses that name for __CatalystChannel__ . Is that a bug?
I do not follow. Can you elaborate please?
Never mind, I didn’t realize that the -c was specific to the example and not for Catalyst scripts in general
If there are more than one channels, is there something to handle this for the -c option?
-c option is for the wavelet_driver, which only produced 1 channel. Are you suggesting we extend that miniapp to produce multiple channels for demostration purposes? Sure, I don’t have any objections there. Shouldn’t be too hard.
Again, thought that -c was a general thing and not specific to this example. Now that I know what’s going on I don’t think that’s necessary to create a multiple channel example at this point.
It would be great to have something available like gridwriter.py and allinputsgridwriter.py
Makes sense. Reported here.
Again, awesome! Will help users immensely IMHO.
What is Frequency for in the Generate Catalyst Script Options window under Global Options?
It is same as every “n-th”. Global options are checked before each extract generator specific trigger options (or live specific trigger options) are checked. Frequency is probably not the right term, but that’s what we’ve used previously so for the lack of a clearer alternative, I left that unchanged.
I guess I’m still not understanding how this global option Frequency will interact with other Frequencies for specific in situ outputs will interact. I haven’t tested yet but if this global option Frequency is 5 and my only writer has a Frequency of 3, say, what time steps will be data be written out?
I guess this adds another question – should the Trigger option be Time or Time Step/Cycle? I know there’s only one option now but hopefully that will change in the future so may as well get it right now 
.