What is the difference between mrf_read.py and mrf_read_data.py?

[lucianpls]

No description provided.

[mcechini]

Seems like the usage between the two is the major difference:

mrf_read_data.py --input [mrf_data_file] --output [output_file] (--offset INT --size INT) OR (--index [index_file] --tile INT)

mrf_read.py --input [mrf_file] --output [output_file] (--tilematrix INT --tilecol INT --tilerow INT) OR (--offset INT --size INT) OR (--tile INT)

[lucianpls]

Doesn't sound like there is enough to keep both. Are you using any of these? The mrf_read_index is another one, you can do the same thing with "od".

[mike-mcgann]

I am using mrf_read.py

[lucianpls]

What for? QC?

[mike-mcgann]

Yes, it is used in our automated end-to-end tests

[mcechini]

We could consider consolidating if needed, but I find mrf_read.py's (--tilematrix INT --tilecol INT --tilerow INT) options to be very helpful.

[jtroberts]

I don't see any strong reason to keep mrf_read_data.py

[lucianpls]

That would be good. Maybe the mrf_read_index could be eliminated too, since it's not that useful? Or have it merged into mrf_read.py.

[jtroberts]

I like the CSV output of mrf_read_index, but rarely every use it. I think it is helpful for debugging and understanding MRFs. It would be nice to merge it into mrf_read and then have only one tool to maintain.