Version 1.6.1 — Delayed

[Juan Conejero]

Hey everybody,

I have decided to delay the release of a new version of PixInsight (1.6.1) for 2-3 weeks. I just wanted to keep you informed because I have written that it would be released "in a few days" on this forum —you know, "days" always has a relativistic meaning here <g>.

The main reason for this delay is that the new version will include some important changes in the way modules are linked to the PixInsight Core application. These changes are intended to solve the current problem of incompatibility between existing modules and new versions of the platform. When I implement the new module linkage model, backward compatibility will definitely be assured. This is a critical, time-consuming task that requires extensive testing.

Another reason to delay the release is the new 64-bit Mac OS X version, which is being a very big headache but that I definitely want to release, even if it isn't as "perfect" as the 32-bit version, for now. Finally, there are some bugs and requested improvements that require a lot of work.

So please be patient, the next version will be much better!

[Carlos Milovic]

Why don't you call it 1.6.2? Just joking

Now a serious proposal: why don't you change the current distribution system. Specially the part related to modules. There may be a "repository" where the compiled modules are stored, and the main application just performs an online search. If a new version, or a new module is found, the user may choose to download it and install.
Even further, the main distribution package may contain only the main application (current PI-xxx distros). Then, all modules are accessed through the repository. If one wants to install the PCL, the same process may be performed.

Could be a lot of work, but will introduce more dynamism...

[bitli]

Yes, in fact the same could be done for the help file updates 

OK, I just needed a few more "days" to finish my scripts...

-- bitli

[RBA]

Will the "preserve FITS headers" be part of this release?

PS: It's not an urgent issue to me, but someone was asking about this somewhere else.

[Juan Conejero]

Hi Rogelio,

Will the "preserve FITS headers" be part of this release?

If you refer to preserving FITS keywords in ImageIntegration, then yes, it will be implemented in the next version.

[pfile]

thanks for the heads-up. it will be worth the wait for the 64-bit macosx version, for me anyway. i've made the leap to snow leopard on my main computer.

[pfile]

any estimated time of arrival for the 64-bit OSX version? i'm running into out of memory problems with large stacks in ImageIntegration...

thanks

[Carlos Milovic]

Juan is preparing the new release. Some announced/proposed features are not ready in optimal way (like the new distribution system, with automatic upgrades) so they'll be delayed for release 1.6.2. So, this 1.6.1 version will be a transitional one, with all discovered bugs fixed, the OSX-64bits support, and the new module installation system (changes to the PCL). It should be ready next week.

[RBA]

Juan is preparing the new release. Some announced/proposed features are not ready in optimal way (like the new distribution system, with automatic upgrades) so they'll be delayed for release 1.6.2. So, this 1.6.1 version will be a transitional one, with all discovered bugs fixed, the OSX-64bits support, and the new module installation system (changes to the PCL). It should be ready next week.

I think that's an intelligent decision. The automatic upgrades (and probably other new and happy features) can wait a bit, but there were a few annoying things in 1.6 that I'll be happy to leave behind once and for all - such as the one that forces me to reset the settings because some process dialogs just decide not to show up within the visible screen.

 

[Nocturnal]

Actually I was really hoping to not have to deal with the persistent explorer windows during my presentation. Bummer. The auto update stuff is nice but mere icing. Project capability and PCL decoupling are more important to me. Well, that and the documentation framework Juan and I discussed who knows how long ago. Sometime last year.

Just griping Juan You do a tremendous job with PI. I don't know how you got it all done.

[pfile]

Juan is preparing the new release. Some announced/proposed features are not ready in optimal way (like the new distribution system, with automatic upgrades) so they'll be delayed for release 1.6.2. So, this 1.6.1 version will be a transitional one, with all discovered bugs fixed, the OSX-64bits support, and the new module installation system (changes to the PCL). It should be ready next week.

great! thanks for the update. i had to resort to cutting my stack into pieces with the region of interest tool... a lot of extra work.

[Juan Conejero]

Just a bit of patience, it is almost ready — a matter of 1-2 days!

Sorry for all the inconveniences caused to all users that are suffering bugs in 1.6.0... I really have been unable to get this made more quickly.

[mmirot]

Any real enhancements  for 1.6.1 ? Or just bug fixes.

Max

[Juan Conejero]

There are lots of enhancements, in fact, although none (almost) of the "spectacular things" that I had planned. Just out of my (poor) memory:

- First 64-bit version for Mac OS X. It is 100% production stable although still tagged as "experimental" due to some graphical glitches.

- First 32-bit and 64-bit versions for FreeBSD/X11. Although they won't be available in the initial release, they will be published during August-September. These will be Tier-1 releases, comparable in all respects to the reference Linux/X11 versions.

- StarAlignment: Selectable/automatic interpolation algorithm (including all the algorithms available in Resample, for example), improved frame adaptation feature, improved console information output.

- ImageIntegration: New persistent file cache, new Linear Fit Clipping rejection algorithm.

- ImageCalibration: New DefectMap tool.

- PCL: A completely new interface between modules and the Core application. Now compatibility of existing modules is guaranteed for all future PI and PCL releases.

- PCL: Important changes in PCL's multithreading infrastructure (this improves performance of all processes and the core application).

- Color management: Integration of LCMS version 2 (more accurate and faster color calibration). All the color management functionality is now provided by the Core application (previously all modules had to be linked against LCMS).

- GUI: Refactored ProcessExplorer. Now all featured scripts are accessible from the ProcessExplorer window, so they can be added to favorites, for example.

- FITS support: Added an option to correctly interpret signed FITS images storing physical pixel values.

and many things that I must review my notes to recall.

There are literally hundreds of bug fixes. This version aims to be extremely stable on all platforms. Although many changes are not visible on the surface, it builds the foundations to a new major release which will include important new features.

[vicent_peris]

So 1.7 is coming! 

To me, simply the new automatic update system would be enough to change to 1.7.


V.