Open ksunden opened 5 years ago
I will mention the existence of wt.collection.from_directory
(oft forgotten)
in the really old days, there was a function in kit
that chewed through a directory and generated "default" images for all of the .data files it found (the same representations that you would get automatically from PyCMDS)---as far as I know that function got used exactly once, for what its worth
I think that this is a bit of a maintenance nightmare, and it just won't get a lot of use
@ksunden I suggest that you simply write your own little bash script for your own machines---that way it can be simple and you won't have to worry about the parameterization nightmare
with the way WrightTools is moving (towards .wt5 files), such a tool will become less-than-useful for non-PyCMDS users
Options:
--from/-f=wt
which from method to use, default towt.open
--save/-s=[FILENAME]
save image/gif, optional filename, default to dataname with proper extension, if not specified, callplt.show
--format/-F
file format to save in, default to png/gif depending on dimensionality--xaxis/-x
expression for x axis--yaxis/-y
expression for y axis--interact/-i
use interact rather than quick--channel/-c
which channel to use, default 0--local/-l
local colormap/yaxis--local-contours/-L
default true--at/-a
chop intomaybe requires a transform argument to be even more useful, but need to think how that would be passed in (ast.literal_eval might work, and is reasonably safe, but may not be as userfriendly)
Thoughts? Good Idea, bad idea?
I just had the idea as I was looking at data that was not automatically plotted (as they are motortunes) and was thinking how easy it would be to do in bash, rather than python (which, mind you is only mildly harder).