I don't understand the last comment vey well:

-the fiber bundle and the fiducial list are conceptually linked for this function, but need to be manipulated separately. From a user perspective I have a streamline with a controller (list, model, ROI) and a set of parameters to modulate the effect of the controller.

Let's not change the name to streamlines (we have used Fiber Bundles consistently and should not change it here).

Again, if I have two separate fiber bundles with two fiducial seeds. I keep them separate, because I would like to extract quantitative measures from each of them. I would like to go back and forth between them while optimizing their location. Now, I have to switch each fiducial and each fiber bundle separately and have to disable and enable tract seeding in a complicated sequence. Its easy to make a mistake in the process.

This seems like what you are doing, if I'm not wrong, is working with two fiducial seeding module instances simultaneously (one for each fiducial/streamline combination). Then the problem is that the outputs of both modules instances are conflicting.

We don't have quantitative measurement extraction from fiber bundles yet.

Is this a new use-case?

yes and not on your immediate todo list. I was just trying to describe a second scenario to clarify.

Included seeding node name into output FiberBundle name.

I would like to reopen the issue on how to improve the UI when switching between fiducial lists.
Following use case:

I have created two fiducial lists, each containing several fiducials. Each fiducial list has a fiber bundle associated with it.
-When creating the fiberbundle, it should take the fiducial list as part of the fiber bundle name.
-I would like to switch the active fiber bundle/fiducial list to adjust parameters. It would be good to be able to do that with a single click. How about an editable table with the following columns: Active/inactive, visible/invisible, fiducial list, fiberbundle

in the previous node I meant to say: node name included in the fiber bundle name, but can we drop the vtkMRML prefix?

I dropped vtkMRML prefix from the fiber name.
Not sure I understand the second request. Is it needed before RSNA?

Its ok for now. we can defer the second request