Standardizing the code structure accross MegaPose and Cosypose, in particuliar:
API Detector (Done)
[API Coarse
API Refiner
—> Standardizing the two approaches would then make it possible to create a more modular architecture for integrating other methods.
Decoupling detection / pose estimation. Currently prediction_runner and pose_estimator handle this... Decoupling would allow greater flexibility.
in megapose/model/pose_rigid, move PosePredictorOutputCosypose elsewhere, but where?
More generally, some code is duplicated between MegaPose and CosyPose (pose_predictor.py, ...). A refactoring of the code to make a general API for HappyPose would be needed. For now, it is similar in both repositories but some work is still needed to make something really clean.
Currently, there are pointers between pose_estimators. For example, CosyPose use the evaluation of MegaPose, which is stored in pose_estimators.megapose. This should be looked at, as a pose_estimator should probably import only from itself and the toolbox part.
If re-training CosyPose (if necessary?) Adapt object names to choices made in MegPose (change from obj-000001 to ycbv_obj-000001, for example, in the config of each model).
For CosyPosetraining, pose_training.py is working on a single GPU but it seems that it doesn't work on Jean Zay. More investigation on why is needed. detector_training.py shouldn't be working yet, as no one worked on it.
Rewriting of the repo using more recent technologies (e.g. PytorchLightning, Weight&Biases)
Update of the Neural Backbone (Yolo for detection ?, PoseEstimator ?)
A good look over the code to remove potentially useless elements (many (unused?) scripts ...) -> Compare with entry points and uses cases?
No particular order in the list
Standardizing the code structure accross
MegaPoseandCosypose, in particuliar:Decoupling detection / pose estimation. Currently
prediction_runnerandpose_estimatorhandle this... Decoupling would allow greater flexibility.in
megapose/model/pose_rigid, movePosePredictorOutputCosyposeelsewhere, but where?More generally, some code is duplicated between
MegaPoseandCosyPose(pose_predictor.py, ...). A refactoring of the code to make a general API forHappyPosewould be needed. For now, it is similar in both repositories but some work is still needed to make something really clean.Currently, there are pointers between
pose_estimators. For example,CosyPoseuse the evaluation ofMegaPose, which is stored inpose_estimators.megapose. This should be looked at, as apose_estimatorshould probably import only from itself and thetoolboxpart.If re-training
CosyPose(if necessary?) Adapt object names to choices made inMegPose(change fromobj-000001toycbv_obj-000001, for example, in the config of each model).For
CosyPosetraining,pose_training.pyis working on a single GPU but it seems that it doesn't work on Jean Zay. More investigation on why is needed.detector_training.pyshouldn't be working yet, as no one worked on it.Rewriting of the repo using more recent technologies (e.g. PytorchLightning, Weight&Biases)
Update of the Neural Backbone (Yolo for detection ?, PoseEstimator ?)
A good look over the code to remove potentially useless elements (many (unused?) scripts ...) -> Compare with entry points and uses cases?
Docker/singularity/apptainer for
Happypose?