Add channel naming back into Ashlar 1.18 wrapper

[CameronFRWatson]

In old versions of the Ashlar tool wrapper, channel naming in the XML metadata was handled by a Python script that updated the image pyramid to a BF6-compliant pyramid. This step is no longer necessary, so we got rid of the script in the wrapper for Ashlar 1.18. A consequence of this was losing the ability to name marker channels as a part of the Ashlar Galaxy tool execution. We could either:

• Leave current functionality, and then make rename_tiff_channels a standard step after Ashlar
• Create a new script for channel naming to replace the old one so it still happens in one step

[jgoecks]

I'm in favor of simplicity for the user, which I think would be the second option so that Ashlar + channel renaming can be done in a single step/tool execution. If there are instances where channel renaming needs to be done independent of Ashlar, a separate tool could be developed.

…

On Mon, Mar 18, 2024 at 6:08 PM Cameron Watson ***@***.***> wrote: In old versions of the Ashlar tool wrapper, channel naming in the XML metadata was handled by a Python script that updated the image pyramid to a BF6-compliant pyramid. This step is no longer necessary, so we got rid of the script in the wrapper for Ashlar 1.18. A consequence of this was losing the ability to name marker channels as a part of the Ashlar Galaxy tool execution. We could either: - Leave current functionality, and then make rename_tiff_channels a standard step after Ashlar - Create a new script for channel naming to replace the old one so it still happens in one step — Reply to this email directly, view it on GitHub <#62>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGXMEJSZQ37WFWDTBNZQADYY5QUHAVCNFSM6AAAAABE4NSCE6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGE4TGNBWHEYTMOA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>