When updating a beta database to the current working version, there was initially a crash that prevented the update from running due to data being inserted in the wrong order in the REFINEMENT_PACKAGE_ASSETS table. @timothygrant80 allowed this update to actually complete by creating a temp table that stores the data from the old database and inserts it into the updated database, with the output_pixel_size being pulled from each corresponding REFINEMENT_PACKAGE_CONTAINED_PARTICLES_, and inserted into the REFINEMENT_PACKAGE_ASSETS table based on REFINEMENT_PACKAGE_ASSET_ID.
With the update able to complete, there was another issue that cropped up, which was the inability to use any existing classifications or refinement results, as needed values were stored as 0.0. This stemmed from the addition of 9 columns to the CLASSIFICATION_RESULT_ and REFEINEMENT_RESULT_ tables. To fix this, I added code that compares the pixel size in these two tables with the value stored in REFINEMENT_PACKAGE_CONTAINED_PARTICLES_ , and if different, updates the values for pixel size, spherical aberration, microscope voltage, and amplitude contrast columns, 4 of the 9 additions, which were not present in the beta database.
Fixes # (issue)
I have rebased my feature branch to be current with the master branch using to minimize conflicts and headaches
[x] yes
[ ] no
Which compilers were tested
[x] g++
[x] icpc
[x] clang
[ ] other (please specify)
These changes are isolated to the
[x] gui
[x] core library
[ ] gpu core library
[ ] program it modifies
How has the functionality been tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.
[x] Tested manually from GUI
[ ] Tested manually from CLI
[ ] Passed console tests
[ ] Passed samples functional testing
[ ] other (please specify)
Checklist:
[x] I have not changed anything that did not need to be changed
[x] I have performed a self-review of my own code
[ ] I have commented my code, (w.r.t. why), particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation {Ok to pass for now}
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules
Description
When updating a beta database to the current working version, there was initially a crash that prevented the update from running due to data being inserted in the wrong order in the
REFINEMENT_PACKAGE_ASSETStable. @timothygrant80 allowed this update to actually complete by creating a temp table that stores the data from the old database and inserts it into the updated database, with theoutput_pixel_sizebeing pulled from each correspondingREFINEMENT_PACKAGE_CONTAINED_PARTICLES_, and inserted into theREFINEMENT_PACKAGE_ASSETStable based onREFINEMENT_PACKAGE_ASSET_ID.With the update able to complete, there was another issue that cropped up, which was the inability to use any existing classifications or refinement results, as needed values were stored as 0.0. This stemmed from the addition of 9 columns to the
CLASSIFICATION_RESULT_andREFEINEMENT_RESULT_tables. To fix this, I added code that compares the pixel size in these two tables with the value stored inREFINEMENT_PACKAGE_CONTAINED_PARTICLES_, and if different, updates the values for pixel size, spherical aberration, microscope voltage, and amplitude contrast columns, 4 of the 9 additions, which were not present in the beta database.Fixes # (issue)
I have rebased my feature branch to be current with the master branch using to minimize conflicts and headaches
Which compilers were tested
These changes are isolated to the
How has the functionality been tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.
Checklist: