Hello all, I've just placed two new runs up onto MilkyWay@home: -de_nbody_08_06_2019_v176_40k__dataExpand__1 -de_nbody_08_06_2019_v176_40k__dataExpand__2 These runs are going to search over a larger phase space, however, due to the technological limitations of simulating incredibly dense dwarf galaxies, a significant portion of this phase space will be skipped. This limitation has been placed in previous runs using the current version of Milkyway_nbody, however, the larger phase space will make this more apparent. We set up our lua file such that runs with abnormally long runtimes will only take a few seconds to complete and return the worst case likelihood score. As credits are calculated dynamically for Nbody, it may take a few runs for Milkyway@home to assign the proper amount of credits. We plan on adding another expanded data run once de_nbody_07_10_2019_v176_40k__data__7 converges. Thank you for your support, Eric

By milkyway@home at 2019-08-06

Hi Everyone, Looking at all of the previous runs (including those from previous projects), there are patterns of interesting and unexpected behavior from the optimization results. In order to better understand these results, I have planned a series of extensive testing runs. These tests will allow us to learn how the optimization routine's responds to specific circumstances and inputs. I will make a comment attached to this post describing the tests & reasons for the tests in greater detail if anyone is interested. EVERYTHING IS WORKING AS INTENDED. These results are not entirely understood, not incorrect. I don't expect to invalidate any results from this project, but I do plan on actually producing more, better results as I learn why the optimizer outputs what it does. I am rolling out the first 2 series of tests, and have released the runs on the server. The names of these runs are: de_modfit_14_bundle5_testing_4s3f_1 de_modfit_14_bundle5_testing_4s3f_2 de_modfit_14_bundle5_testing_4s3f_3 de_modfit_14_bundle4_testing_3s4f_1 de_modfit_14_bundle4_testing_3s4f_2 de_modfit_14_bundle4_testing_3s4f_3 Please let me know if you experience any problems with these runs. Thank you all for your help with this project! Best, Tom

By milkyway@home at 2019-07-29

Hi Everyone, I just put some new Separation runs up on the server and took down the old ones. You may still see new workunits from old runs in your queues for a few days as those runs finish validating. The names of the new runs are: de_modfit_80_bundle4_4s_south4s_bgset de_modfit_81_bundle4_4s_south4s_bgset de_modfit_82_bundle4_4s_south4s_bgset de_modfit_83_bundle4_4s_south4s_bgset de_modfit_84_bundle4_4s_south4s_bgset de_modfit_85_bundle4_4s_south4s_bgset de_modfit_86_bundle4_4s_south4s_bgset An error processing a flag in the parameter files has been fixed and updated runs have been released. These runs are confirmed to be returning results as of 10 PM on 7/24. I apologize for the inconvenience. The names of the new runs are: de_modfit_80_bundle4_4s_south4s_bgset_2 de_modfit_81_bundle4_4s_south4s_bgset_2 de_modfit_82_bundle4_4s_south4s_bgset_2 de_modfit_83_bundle4_4s_south4s_bgset_2 de_modfit_84_bundle4_4s_south4s_bgset_2 de_modfit_85_bundle4_4s_south4s_bgset_2 de_modfit_86_bundle4_4s_south4s_bgset_2 As these runs optimize we may see increased invalidated returns with the stripe 84 and 85 runs. This is a known issue that I believe has something to do with a data cut made in those stripes. If/when this starts happening and the stripes are sufficiently optimized, I will take them down so you all don't have to worry about crunching invalidated WUs. If you have any questions/comments/concerns, please feel free to post them here. Thanks for all your support! Best, Tom

By milkyway@home at 2019-07-24