Bogus "not xml" warning (minor bug?)

Hi,

Import beam shift warns me that the path I have input does not end in xml, when it does end in xml.

Also I wonder if there is a way to make the string matching more automated? It always requires a bit of manual mucking about editing how much to cut from prefix/suffix but it seems like a string matching operation that should be possible to automate except in edge cases (which could still be handled manually)?

Cheers

Oli

String matching should be easy if the output is from EPU and not manually shuffled around. For all of our datasets, across multiple version of EPU, in the Beam Shift Import section, it’s blank - blank - 8 - blank - 4 (default) from the top down. If you collect in TIFF, it’ll be different, though - maybe 13 or 14 rather than 8?

I’ve never seen that warning. If you make the *xml at the end *.xml, does it go away? CryoSPARC might be expecting that period to differentiate between filename and extension.

1 Like

Yes that is probably it… still feels like if it ends with xml it shouldn’t trigger this warning