Create Coseismic_Requirement_Validation-Approach2.ipynb#26
Create Coseismic_Requirement_Validation-Approach2.ipynb#26dbekaert merged 8 commits intonisar-solid:mainfrom
Conversation
New version of Coseismic notebook with approach 1 and 2 code added, along with other changes.
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
|
@EJFielding Suggest not to change names of the notebook versions as then we loose the ability to track versions using github or compare with the notebook tool. If a name change is needed please use git mv capabilities. |
|
View / edit / reply to this conversation on ReviewNB dbekaert commented on 2022-05-02T03:12:14Z Noticed this traceback error. Does not look like a failure, but any thoughts as to why this occurred?
EJFielding commented on 2022-05-02T03:15:55Z Yes, because I used the staged data, the yunjunz commented on 2022-05-02T03:32:14Z I just tried to copy over the printout custom template and tested on the San Francisco Bay example dataset, and could not re-produce the error. I can't think of causes on top of my head. EJFielding commented on 2022-05-02T04:23:16Z I think it is because we are using EJFielding commented on 2022-05-02T04:24:46Z Does everybody else always modify their MintPy template file every time they run mgovorcin commented on 2022-05-02T16:26:08Z I notice this trackback error before, and believe it is associated with staged ifgramStack.h5 and "mintpy.network.excludeIfgIndex" flag. Initially, the stack is staged with excluded 6 ifgs, so when we change it to use all pairs, I guess MintPy cannot find them and raise the error. Should we leave it like this or staged the data again with all included pairs? EJFielding commented on 2022-05-02T16:30:03Z Hi Marin, I believe the mgovorcin commented on 2022-05-02T16:38:41Z I just reproduced the error. Believe it is associated with the update of smallbaseline config file as it is different than the staged one (having also different timestamp). So, guess MintPy is trying to reload the data but it cannot find ARIA stack folder and raise the error. yunjunz commented on 2022-05-02T17:14:32Z @mgovorcin could you show here how to re-produce the error? preferably on laptop for me to easily test. EJFielding commented on 2022-05-02T17:29:21Z @yunjunz I got the same error on my Mac laptop. It happens when we download the staged data that does not include the ARIA-tools products and run the script a second time in the same directory. mgovorcin commented on 2022-05-02T17:41:49Z @yunjun try to run the notebook with these changes:
EJFielding commented on 2022-05-02T18:04:23Z @yunjunz Looking at it again, it can also be due to MintPy parsing. It thinks that it needs to change the configuration because of the backslash that is added as an escape for the asterisk. mintpy.load.azAngleFile: ../azimuthAngle/\*.vrt --> ../azimuthAngle/*.vrt yunjunz commented on 2022-05-02T20:32:30Z Thank you @EJFielding and @mgovorin, I was able to re-produce the error. The issue is in the template updating code: the staged default template option "mintpy.network.excludeIfgIndex = [123,124,125]" has "[]" included, these are special characters for EJFielding commented on 2022-05-02T23:03:10Z Thanks, @yunjunz! I pulled the new version of MintPy to my Mac and run the notebook again, and it is working well without the errors. It is re-running the network inversion without the excluded scenes. |
|
View / edit / reply to this conversation on ReviewNB dbekaert commented on 2022-05-02T03:12:14Z Same in this cell output.
EJFielding commented on 2022-05-02T03:16:25Z Yes, the problem affects all the yunjunz commented on 2022-05-02T03:33:12Z This means all the smallbaselineApp calls in this notebook are not actually run. EJFielding commented on 2022-05-02T23:03:30Z Now this is fixed. |
|
View / edit / reply to this conversation on ReviewNB dbekaert commented on 2022-05-02T03:12:15Z Seems to be impacted here by the coseismic. Was not the case before. EJFielding commented on 2022-05-02T03:18:06Z This depends on whether the velocity fit was done with the coseismic step or not. If the coseismic step is not estimated, then the linear velocity absorbs the coseismic. EJFielding commented on 2022-05-02T03:22:59Z The staged |
|
@dbekaert OK, I removed the old version and moved the new version to the same name. |
|
hi @EJFielding Were you running this from already existing run? I noticed some error messages in the mintpy output which seems not to have stopped from continue the running. The version is slightly different from what was used on OSL. One plot i noticed for secular or mean velocity showed now some coseismic signal. Stats look good! |
Worked well, thanks for doing that! |
|
Yes, because I used the staged data, the View entire conversation on ReviewNB |
|
Yes, the problem affects all the View entire conversation on ReviewNB |
|
This depends on whether the velocity fit was done with the coseismic step or not. If the coseismic step is not estimated, then the linear velocity absorbs the coseismic. View entire conversation on ReviewNB |
|
The staged View entire conversation on ReviewNB |
|
I just tried to copy over the printout custom template and tested on the San Francisco Bay example dataset, and could not re-produce the error. I can't think of causes on top of my head. View entire conversation on ReviewNB |
|
This means all the smallbaselineApp calls in this notebook are not actually run. View entire conversation on ReviewNB |
|
@mgovorcin did you experience this on OSL? Is something missing from the clean-up? |
|
I think it is because we are using View entire conversation on ReviewNB |
|
Does everybody else always modify their MintPy template file every time they run View entire conversation on ReviewNB |
|
I notice this trackback error before, and believe it is associated with staged ifgramStack.h5 and "mintpy.network.excludeIfgIndex" flag. Initially, the stack is staged with excluded 6 ifgs, so when we change it to use all pairs, I guess MintPy cannot find them and raise the error. Should we leave it like this or staged the data again with all included pairs? View entire conversation on ReviewNB |
|
Hi Marin, I believe the View entire conversation on ReviewNB |
|
I just reproduced the error. Believe it is associated with the update of smallbaseline config file as it is different than the staged one (having also different timestamp). So, guess MintPy is trying to reload the data but it cannot find ARIA stack folder and raise the error. View entire conversation on ReviewNB |
|
@mgovorcin could you show here how to re-produce the error? preferably on laptop for me to easily test. View entire conversation on ReviewNB |
|
@yunjunz I got the same error on my Mac laptop. It happens when we download the staged data that does not include the ARIA-tools products and run the script a second time in the same directory. View entire conversation on ReviewNB |
|
@yunjun try to run the notebook with these changes:
View entire conversation on ReviewNB |
|
@yunjunz Looking at it again, it can also be due to MintPy parsing. It thinks that it needs to change the configuration because of the backslash that is added as an escape for the asterisk. mintpy.load.azAngleFile: ../azimuthAngle/\*.vrt --> ../azimuthAngle/*.vrt View entire conversation on ReviewNB |
|
Thank you @EJFielding and @mgovorcin, I was able to re-produce the error. The issue is in the template updating code: the staged default template option "mintpy.network.excludeIfgIndex = [123,124,125]" has "[]" included, these are special characters for View entire conversation on ReviewNB |
|
Thanks, @yunjunz! I pulled the new version of MintPy to my Mac and run the notebook again, and it is working well without the errors. It is re-running the network inversion without the excluded scenes. View entire conversation on ReviewNB |
1 similar comment
|
Thanks, @yunjunz! I pulled the new version of MintPy to my Mac and run the notebook again, and it is working well without the errors. It is re-running the network inversion without the excluded scenes. View entire conversation on ReviewNB |
|
Now this is fixed. View entire conversation on ReviewNB |
Added alert boxes to mark results. Other cleanup to reduce number of cells and improve descriptions.
|
View / edit / reply to this conversation on ReviewNB EJFielding commented on 2022-05-05T21:36:06Z All the GNSS fits change by a tiny amount because a few new dates are included in the time-series. |
Fixed bug where not all Method 2 uses of `dist` were changed to `M2dist`.
dbekaert
left a comment
There was a problem hiding this comment.
Looks good with all the fixes made.
New version of Coseismic notebook with approach 1 and 2 code added, along with other changes.