Missing filenames in example networks

[florianlink]

First of all, great work! This is the nicest usage of the MeVisLab Path Tracer that I know of.

I downloaded the zip and tried the example networks, but they all had no filenames in the loader modules.

I managed to load them manually, but wouldn't it be much nicer if they would already contained the paths to the example data?

You could also add a RunPythonScript to each network which loads all datasets and presses the appropriate buttons automatically.

[SimboMac]

Hi Florian,

Sorry for the late reply—I was on holiday.

Thanks so much for your kind words. I'm really glad to hear that you like our work with MeVisLab/MeVis Path Tracer and appreciate you taking the time to explore the networks.

I see what you mean about preloading the paths for the example data and how making things more straightforward with a script could help. To solve/minimize the impact of the issue you mentioned, rather than modifying the network files (I think I might be able to add the path to the reader but I have no idea about the script to automate the modules),I believe it’s sufficient to package the step-by-step guide (which clearly states at the beginning where the files needed to replicate the examples are) directly into the SmARTR networks archive and include a readme.txt file to further clarify where everything is located. I will update the file content ASAP (hopefully today).

In my view, the goal of the step-by-step guide and the examples provided is to encourage users to explore the features of the software modules hands-on and better understand how each part fits together. I believe this approach could be especially helpful for people like me—without any coding background or knowledge—so they can gain enough understanding to make the most of the SmARTR networks, modify them, or even build their own networks from scratch to suit specific visualization needs.

That said, I understand that getting the guide from the link might not be obvious. I also noticed that the link no longer directly downloads the guide but simply redirects to the article page—that wasn’t the case before, and that might be the root of the problem. I’ll make sure to update it.

Thanks again for reporting the issue and for the suggestion. If anything else comes up or you have more ideas, feel free to reach out.

Have a great day!

Cheers,

Simone