Update mm_rework to match mm_rework_lingfeng for comparison - #25
Open
wei-lingfeng wants to merge 15 commits into
Open
Update mm_rework to match mm_rework_lingfeng for comparison#25wei-lingfeng wants to merge 15 commits into
wei-lingfeng wants to merge 15 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request is just to show the updates that make mm_rework and mm_rework_lingfeng different. Since the plan is to go with mm_rework_lingfeng eventually, it does not need to be actually merged. I will open another pull request to merge mm_rework_lingfeng into dev and eventually into main.
motion_model_inputcolumn to do so. This should not be something the package imposes. Changen_pts_req=3.x_wt = 1/xe**2, thensigma = 1/x_wt**0.5would result in floating-point errors, and in multiple iterations of align, this error is cumulative. Change: Changed tomotion_model.calc_sigma, which only returnssigma_x = xeornp.sqrt(xe), that can be input into scipy directly. Weight is only calculated when needed (most of the time not)curve_fit. BUG:absolute_sigmais not used. Change: Now replaced everything withcalc_sigmaand addedabsolute_sigmatimes=Times(mjd + 2400000.5, format=’jd’, scale=’tdb’)totimes=Times(mjd, format=’mjd’, scale=’tdb’)absolute_sigma:absolute_sigma=Falsepreviously, nowabsolute_sigma=True. We need to decide which one we want by default.test_MosaicSelfRef_vel. This failure is already present at this point. But mm_rework_lingfeng has no issues with this.Example showing scipy’s curve_fit is equivalent to propagated uncertainty (error on the mean):
Output: