Closes #19, "Allow frames to start at number other than zero."
Resolves an issue first encountered by @gouthamr321, where datasets that started at timepoints other than 0 would show an error when loaded into the colorizer.
This update makes the automatically-generated frame paths explicit, and adds an entry point for users to change the frame paths if needed.
Changelog:
Adds a helper method, generate_frame_paths, that can be configured with an image prefix, image suffix, and a starting offset.
Removes the num_frames argument from writer.write_manifest and replaces it with writer.set_frame_paths.
The manifest now performs a validation step before writing, warning the user if there are any missing image files.
Closes #19, "Allow frames to start at number other than zero."
Resolves an issue first encountered by @gouthamr321, where datasets that started at timepoints other than 0 would show an error when loaded into the colorizer.
This update makes the automatically-generated frame paths explicit, and adds an entry point for users to change the frame paths if needed.
Changelog:
generate_frame_paths, that can be configured with an image prefix, image suffix, and a starting offset.num_framesargument fromwriter.write_manifestand replaces it withwriter.set_frame_paths.