Closed lanelee44 closed 2 years ago
Both debugging functions are present on my end. Double check when you get a chance.
On Tue, Feb 22, 2022 at 2:08 PM Aditya Savara @.***> wrote:
@.**** requested changes on this pull request.
Unless I am mistaken, the debuggingExportIndividualItem function is not here. So if somebody tries to turn debugging on, the program will crash.
— Reply to this email directly, view it on GitHub https://github.com/AdityaSavara/MSRESOLVESG/pull/286#pullrequestreview-890245004, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVKGLIUZJMD3UTFXRA5PJK3U4PNLPANCNFSM5PBRSJSQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
Yes, you are right. The debugging functions are here. Github did not color them the way I expected so I mistook those for commented out code. I have run the unit tests. All unit tests passed. I am accepting the merge into master. Update your master locally and delete this branch.
Added new debugging functions. Also, updated all variables that include reciprocal correction factors to include "reciprocal" in the variable's name.