In #142, two other issues have been brought to light when wanting to produce an example to illustrate the problem of initialisation of this ticket (#142). Because #142 is now solved, I open this new one to keep in mind the two other problems (problem1 and problem2, vide infra):
Steps to reproduce:
Launch Mia
Import or open a project with for ex. one anat.nii and one func.nii
Go to Pipeline Manager
In the New Pipeline tab, drag and drop the Realign brick from the mia_processes library
Right click on the Realign brick and choose Export all unconnected plugs
Click on the inputs node then click on the Filter button for the in_files parameter, in the controller (right part of the window).
Select the func.nii from the database.
Pipeline > Initialize pipeline
Open a new tab then drag and drop for example a Smooth brick from the mia_processes library
Right click on the smooth1 brick and choose Export all unconnected plugs
Click on the inputs node then click on the Filter button for the in_files parameter, in the controller (right part of the window).
=> Problem1, we have now only access to the anat.nii scan !
Select the anat.nii file from the database.
Pipeline > Initialize pipeline
Go back to the first tab
Pipeline > Run pipeline
With the last modification (cf41061), this last line "Pipeline > Run pipeline" is no longer possible in the other tab. But when it was possible, because the database was not synchronised with the pipeline, the run was not realised but the status bar was displaying: Pipeline "" has been correctly executed
=> Problem2, this indicates that the message at the end of an execution is not correctly made, this could happen in another example.
In #142, two other issues have been brought to light when wanting to produce an example to illustrate the problem of initialisation of this ticket (#142). Because #142 is now solved, I open this new one to keep in mind the two other problems (problem1 and problem2, vide infra):
Steps to reproduce:
With the last modification (cf41061), this last line "Pipeline > Run pipeline" is no longer possible in the other tab. But when it was possible, because the database was not synchronised with the pipeline, the run was not realised but the status bar was displaying: Pipeline "" has been correctly executed => Problem2, this indicates that the message at the end of an execution is not correctly made, this could happen in another example.