Show Posts
1
Uncertainty Quantification (quoFEM) / FEATURE REQUEST: Log or Progress Tab in GUI
« on: June 16, 2020, 06:27:02 PM »
Hello,
After attending both sessions on quoFEM (15-16/06/2020), I understand that there is log file for this framework that the developers could use to track the processes inside quoFEM if a user has problems. I wanted to ask FMK and Adam:
My reasoning for this feature is:
It could help us quickly look back at what has already been processed / what we already did. So if a lengthy process (of 1000 samples rather than 100 samples) is complete, I can return to the software and see my progress from the logging tab. And also check my history of parameter choices, algorithm choices, imported file names, etc... The log text could just be a minimal standard that is triggered by every major user interaction with the software: "Browse/Choose", "Run". Progress of an algorithm that is running from other software might be tricky, but probably very much desirable too!
It could also include useful warnings to the user, if the user decides to press Run when any necessary parameters from the tabs were empty or incomplete. Although there is a warning message that could pop up on the top of the GUI, keeping track of it might be good?...
Thank you for the consideration and this promising framework.
Ahmed Torky
After attending both sessions on quoFEM (15-16/06/2020), I understand that there is log file for this framework that the developers could use to track the processes inside quoFEM if a user has problems. I wanted to ask FMK and Adam:
Quote
Is it possible to have a logging tab inside of the GUI (one that is for the USER)?"Adam asked during the session if this is for server or local use. I guess it could be beneficial for both, but it could be minimal...
My reasoning for this feature is:
It could help us quickly look back at what has already been processed / what we already did. So if a lengthy process (of 1000 samples rather than 100 samples) is complete, I can return to the software and see my progress from the logging tab. And also check my history of parameter choices, algorithm choices, imported file names, etc... The log text could just be a minimal standard that is triggered by every major user interaction with the software: "Browse/Choose", "Run". Progress of an algorithm that is running from other software might be tricky, but probably very much desirable too!
It could also include useful warnings to the user, if the user decides to press Run when any necessary parameters from the tabs were empty or incomplete. Although there is a warning message that could pop up on the top of the GUI, keeping track of it might be good?...
Thank you for the consideration and this promising framework.
Ahmed Torky