Open abdulazizab2 opened 2 years ago
Solved by utilizing cfg_options instead of splitting config files. However, is this best practice approach to split a model configuration?
For an example, if I build the detector from the original [config] say:
x = build_detector( base.model.roi_head, test_cfg=action_det_base_config.get("test_cfg")) It will build the model. However, after loading the checkpoint it will produce a warning that some of the keys in the source are missing. But after inspecting the variable, the values exist. I guess the problem is with the way I am trying to build the model. Any hint or tips ?
Did not try this method. But the deploy of spatial-temporal detection models will be supported soon. Please stay tuned.
I appreciate your efforts and I am tuned for integration action repo with deployment repo. Hope I can contribute too.
Did not try this method. But the deploy of spatial-temporal detection models will be supported soon. Please stay tuned.
When will it be supported?
I have searched related issues and tried to do the implementation with no success.
I am aiming to split a spatio-temporal action detection model into two configuration files. Base and Head A configuration for the backbone (type=fastrcnn) and a configuration for roi_head. This will help me to export the backbone into onnx.
The problem is, I can't load the model from the config once I changed the configuration. Is there an example to follow. As every time I want to load base or head I get errors thrown
I get an error that the model type is missing, I tried to use different types but no success.