Skip to content
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

Regarding the replacement of CS21/CS22/C30/C40/C50 in the grace_input_months function? #128

Open
SingyuTang opened this issue Jun 12, 2023 · 4 comments

Comments

@SingyuTang
Copy link

Hello, in the grace_input_months function, why do CS21/CS22/C30/C40/C50 set the grace_month greater than 179 (in the source code, grace_month > 176) to replace the GRACE observations with SLR observations? Where is it? It is mentioned in the literature, can you answer or provide a link to the literature? Thanks!

@tsutterley
Copy link
Owner

I typically only replace these harmonics for periods with a single (fully) working accelerometer within the satellite pair (GRACE or GRACE-FO). This is when one of the satellites either has either a degraded or non-operational accelerometer. In these cases, non-gravitational (non-grav) effects may not be fully compensated and can contaminate some degrees and orders within the spherical harmonic solutions. I have some notes written up in the project documentation, and within the peer-reviewed literature, I would refer to Bandikova et al. (2019) . Earlier dates for these harmonics could also be replaced with SLR solutions, however, it is best to keep in mind that the ranging-based solutions are improved after the launch of LARES in 2012.
@strawpants or @jgte might be able to provide some more insight.

@tsutterley
Copy link
Owner

Also, I typically only replace C2,0 and C3,0 with SLR solutions in standard practice. When running spherical harmonic solutions from GFZ, I additionally calculate estimates replacing C2,1, S2,1, C2,2 and S2,2. While I have these as options in the code, doing these replacements should be done with care.

@SingyuTang
Copy link
Author

Thank you very much for your help, I think I should improve the learning of background knowledge, which can help me use this toolkit better.

@tsutterley
Copy link
Owner

Sounds good! Feel free to ask questions here or on the Discussions board.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants