We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, it seems that the location of custom module is both hard coded and implied by the launch location.
For example, a custom module has to be in a directory called custom_modules within the current working directory.
custom_modules
For example, here:
terratorch/terratorch/cli_tools.py
Line 59 in 9912b97
Lines 390 to 397 in 9912b97
terratorch/terratorch/registry/custom_registry.py
Line 6 in 9912b97
I would suggest replacing the hard-cored paths, checking for the path in the following order of precedence:
--module-path
CUSTOM_MODULE_PATH
The text was updated successfully, but these errors were encountered:
@romeokienzler @Joao-L-S-Almeida
Sorry, something went wrong.
thanks @WillTrojak will put it to the sprint list
Joao-L-S-Almeida
Successfully merging a pull request may close this issue.
Currently, it seems that the location of custom module is both hard coded and implied by the launch location.
For example, a custom module has to be in a directory called
custom_modules
within the current working directory.For example, here:
terratorch/terratorch/cli_tools.py
Line 59 in 9912b97
terratorch/terratorch/cli_tools.py
Lines 390 to 397 in 9912b97
terratorch/terratorch/registry/custom_registry.py
Line 6 in 9912b97
I would suggest replacing the hard-cored paths, checking for the path in the following order of precedence:
--module-path
CUSTOM_MODULE_PATH
The text was updated successfully, but these errors were encountered: