-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
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
repo structure #16
Comments
I like the idea. For OPERA we chose the term CSLC to represent Coregistered SLC in general regardless if they are in radar or geo-coordinates. If we want to avoid confusion in that regard, then I suggest to use:
That being said, the name that I really like for GSLC is |
I assume you meant If the geocode SLC executable script can be as short as the current |
I like the changes. A few questions/comments: How does Regarding the common executable, were you thinking the following?
I like the cleanliness and the additional logic doesn't seem too troublesome. That said, I also like the descriptive clarity of current verbose structure. |
I think the run config for radar and geo slc have fundamental differences which we only introduce un-necessary work and complication to the workflow for gaining little or nothing. I suggest we keep the cslc workflows separate for geo and radar coordinates. |
We could make scripts available on the command line using entry_points in setup.cfg. With this, Within compass itself, the |
I like the changes and the suggestions given above. My preference is that the repo re-organization is done after the geocoded burst PR gets merged (less work in addressing conflicts) |
@yunjunz I would like to close this issue. Will you take care of this? Now is a good time to re-organize the repo before we submit other PRs. |
Yes, I will issue a PR soon. Update: below is what I shooting for, after accommodating our discussions above and offline. /COMPASS
/src/compass
s1_cslc.py (add an option to switch bwt geo/radar and call s1_geocode_slc.py for geo workflow)
s1_rdr2geo.py
s1_geo2rdr.py
s1_geocode_slc.py (renamed from geo_cslc.py)
s1_resample.py (renamed from s1_resample_burst.py)
...
/utils
helpers.py
geo_grid.py (renamed from geogrid.py)
geo_metadata.py (renamed from geo_cslc_metadata.py)
radar_grid.py (renamed from reference_radar_grid.py)
runconfig.py
del unwrap_namespace.py (duplicate to wrap_namespace.py)
...
/defaults
s1_cslc_radar.yaml (renamed from cslc_s1.py)
s1_cslc_geo.yaml (renamed from geo_cslc_s1.yaml)
/schemas
s1_cslc_radar.yaml
s1_cslc_geo.yaml
/tests
... |
Seeing the growing COMPASS repo, I am thinking of the following changes:
cslc_s1.yaml
tos1_cslc.yaml
, to be consistent with the script names1_cslc.py
schemas
anddefaults
from withinutils
to the same level asutils
for shoter path, since users will check them frequentlybin
directory for executables, likes1_cslc.py
, as they are really executable scripts. Update: we could add entry_points for executables, without moving them to abin
folder.These lead to a structure as below:
Let me know what do you think please @LiangJYu @vbrancat @hfattahi .
The text was updated successfully, but these errors were encountered: