The fraction of open to globular clusters is highest in the Milky Way and lowest in M31.
Our comparisons of the cluster ages, masses, and metallicities show that our results are basically in agreement with previous studies (where objects in common are available); differences can be traced back to differences in the models adopted, the fitting methods used, and stochastic sampling effects.
I can re-enable it and temporarily replace the archive URL with my fixed version though if you don't have the time to merge the available PR and release a new version right now. Uninstalled the M33Fio plugin as you described (21 mars CET), and installed the fix all through the GUI of Octo Print(restarted as instructed after uninstall and install). I've just printed a test piece, after a complete calibration without a hazzle. Can confirm the fix (https://github.com/foosel/M33-Fio/archive/fix/issue216.zip) and reinstall of m33fio works to resolve the issue. Our photometry includes 387, 563, 616, 580, and 478 objects in the UBVRI bands, respectively, of which 276, 405, 430, 457, and 363 do not have previously published UBVRI photometry.Our photometry is consistent with previous measurements (where available) in all filters.After rolling back to Octo Print version 1.3.1, everything works fine again.
Please let me know if you'd like any additional info from me, and thanks very much.We adopted Sloan Digital Sky Survey ugriz photometry for complementary purposes, as well as Two Micron All Sky Survey near-infrared JHK photometry where available.We fitted the spectral-energy distributions of 671 star clusters and candidates to derive their ages, metallicities, and masses based on the updated minimization routines show that only 205 of the 671 clusters (31%) are older than 2 Gyr, which represents a much smaller fraction of the cluster population than that in M31 (56%), suggesting that M33 is dominated by young star clusters () = 4.25, 5.43, 2.72, and 4.18, respectively.Actual: ['name', 'color', 'axes', 'heated Bed', 'volume', 'model', 'id', 'extruder'] 2017-03-18 ,461 - octoprint.plugin - ERROR - Error while calling plugin m33fio Traceback (most recent call last): File "/home/pi/oprint/local/lib/python2.7/site-packages/Octo Print-1.3.2-py2.7.egg/octoprint/plugin/__init__.py", line 229, in call_plugin result = getattr(plugin, method)(*args, **kwargs) File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint_m33fio/__init__.py", line 5392, in on_event File Locations() File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint_m33fio/__init__.py", line 5273, in set File Locations Printer Profile() File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint_m33fio/__init__.py", line 887, in save Printer Profile self._printer_profile_manager.save(printer Profile, True, not self._settings.get_boolean(["Not Using AMicro3DPrinter"])) File "/home/pi/oprint/local/lib/python2.7/site-packages/Octo Print-1.3.2-py2.7.egg/octoprint/printer/profile.py", line 259, in save self._save_to_path(self._get_profile_path(identifier), profile, allow_overwrite=allow_overwrite) File "/home/pi/oprint/local/lib/python2.7/site-packages/Octo Print-1.3.2-py2.7.egg/octoprint/printer/profile.py", line 374, in _save_to_path raise Invalid Profile Error() Invalid Profile Error In case you're having this problem, here are the (reasonably easy, tested and working) instructions to roll back to Octo Print 1.3.1 in the meantime until this issue is fixed: https://github.com/foosel/Octo Print/wiki/FAQ#how-can-i-revert-to-an-older-version-of-the-octoprint-installation-on-my-octopi-image Use the following command for step 4: The issue probably arises due to the plugin attempting to create/update a printer profile that thanks to not being merged over the default printer profile like it would be when creating it through the UI now lacks a parameter that was introduced with 1.3.2. In light of this I'd seriously recommend people running with this plugin to please also test the release candidates I put out before every stable release.This issue could have been found and circumvented if anyone had done that and reported back.The terminal shows repeated "wait" commands being received, and the connection attempt never times out, it just hangs.