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?
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.
When using the
-cto 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?
If there are more than one channels, is there something to handle this for the
-coption?
-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.
It would be great to have something available like
gridwriter.pyandallinputsgridwriter.py
Makes sense. Reported here.
What is
Frequencyfor in theGenerate Catalyst Script Optionswindow 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.