Created by: amtamasi
We are trying to implement a way to organize registration project information (both metadata and data). Right now, someone running registration for a particular "object of interest" (e.g. PHerc118 Pezzo 1) is the only person who knows where all the necessary files are (e.g. images and hyperspectral data as fixed and moving inputs) for that registration project. They also specify where the output of registration and image stitching goes.
We could like a structure to organize that information and standardize this process pipeline. My (and Chad Nelson's) current idea is to define this as a folder structure. This folder structure needs a class to parse and manipulate the contained information to run registration and stitching. We call this registration package structure a "regpkg".
Here is how an example of how one might use the regpkg interface for registration:
Regpkg regpkg = loadRegpkg('directory/of/regpkg')
auto fixed_input = regpkg.getInput()
auto moving_input = regpkg.getInput()
auto registered_obj = register2D(fixed_input, moving_input)
regpkg.addRegistration(registered_obj, save_to_pkg=True)
Migrated from GitLab issue 31 originally opened by @csparker247 on 2019-10-10.
Created by: amtamasi
We are trying to implement a way to organize registration project information (both metadata and data). Right now, someone running registration for a particular "object of interest" (e.g. PHerc118 Pezzo 1) is the only person who knows where all the necessary files are (e.g. images and hyperspectral data as fixed and moving inputs) for that registration project. They also specify where the output of registration and image stitching goes.
We could like a structure to organize that information and standardize this process pipeline. My (and Chad Nelson's) current idea is to define this as a folder structure. This folder structure needs a class to parse and manipulate the contained information to run registration and stitching. We call this registration package structure a "regpkg".
Here is how an example of how one might use the regpkg interface for registration:
Migrated from GitLab issue 31 originally opened by @csparker247 on 2019-10-10.