Completed Modules Indicator

[dariv]

Sometimes I am multitasking while running ST and forget what module I ran last. Some are obvious, some are not. Might be nice to indicate on the buttons if that module has been run.
Thanks!
-=DaRiv=-

[Russ.Carpenter]

I seem to have the same problem. Of course, the log file has a ton of information, but some kind of history, within the GUI itself, would be welcome.

Russ

[Avocette]

I fully support the idea. Undo would be great to have a dropdown list of actions already completed!

[admin]

Hi all,

The basis for this feature request assumes that processing in StarTools is a simple linear affair - with regards to time flow and signal flow - like it is in less sophisticated software (ex. PI / PS).

Fundamentally, in ST it is not, however (you can read more about how StarTools works here).

I understand it is tempting to see a StarTools workflow as a simple linear process like it is in less sophisticated software, but that is not at all what really happens at the back end.

While "do it once, do it right" workflows are encouraged, revisiting modules and/or using them out of order is a fundamental feature of the processing engine.

Creating a feature that shoehorns an old paradigm (the concept of a "history") into something that on a fundamental level does not work like that at all, would be limiting and misrepresent the software's capabilities.

I hope the above, in combination with the information behind the links helps and makes sense!

[hixx]

hmmm, I think thank might be 2 pairs of shoes:
1) ST's potential workflow: the capability of non-linear workflow, revisiting modules etc.
2) The actually performed user workflow: This indeed is most likely a linear process except modules are being revisited deliberately.
The control is asked for 2) not for 1) as per my understanding

I understand the ask is not to nail the linear thing, but just to make the user aware which module had been run already (even though they still could be revisited or the RESTORE feature could time travel to a previous state).

To satisfy this ask for guidance, there'd be 2 potential options:
1) a GUI change on the buttons as an indication for users without taking away any flexibility. (initial ask)
2) making the log file visible that is existing anyway. E.g. the users could just press a button, a box with the log file content would show to inform the user of processing history. I do not think such feature would indicate any limitation of STs flexibility. It would on top provide the user information on the parameters used in the last run in case he needs to revisit a module

clear skies,
jochen

[Topographic]

I like the last idea of the log file being available by the press of a button (with an option to hide the mask details preferably) and a save possibility. Perhaps an option to run a new log file made available when loading new data.

David

[happy-kat]

STReplay does great and loading a log, and can select from which step to which step etc. to run. At the moment it supports 1.6 flavour, I expect a 1.7 flavour perhaps at some point hopefully.

I do like the idea of a button to open the log file to look at it and showing the end/most recent complete action please, saves me doing it manually.

[Russ.Carpenter]

Hi happy-kat,

I'll just mention that STReplay doesn't work with Mac computers.

I think Topgraphic made a great suggestion: "I like the last idea of the log file being available by the press of a button (with an option to hide the mask details preferably) and a save possibility. Perhaps an option to run a new log file made available when loading new data."

Russ

[BrendanC]

Just noticed this topic. Completely agree - maybe if the button for an already-used module could just be a different colour, greyed out possibly, or have a tick next to it, or something. Very small change, would help quite a lot. I also sometimes find it difficult to know where I was up to if I get distracted, especially if processing takes a while.