h0bb3 / s4rdm3x Goto Github PK

Hello,
I downloaded your compiled release 1.0 and tried running v3xt.jar using Java 11.0.4 and 1.8.0.
The application starts but in the terminal I see the following message:

Could not add system model: data\systems\argouml\argouml.sysmdl - referenced jars do not exist
Could not add system model: data\systems\JabRef\3.7\jabref-3_7.sysmdl - referenced jars do not exist
Could not add system model: data\systems\ProM6.9\ProM_6_9.sysmdl - referenced jars do not exist
Could not add system model: data\systems\sweethome3d\sweethome3d.sysmdl - referenced jars do not exist
Could not add system model: data\systems\teammates\teammates.sysmdl - referenced jars do not exist

Then running the sample experiment does not seem to produce any results, instead it seems to be stuck until I press stop experiment, upon which the application crashes.. Not sure if the second fault is due to the first one or if I'm doing something wrong.

Any pointers?

We need to be able to view the data over the manual mappings. At least in the tooltips.

The way of specifying threads per experiment is clumsy and hard to work with. It would e better to just set the exact number of threads in total that should be usable. This would in essence mean that you can have fewer threads than experiments, i.e. experiments without threads would have to wait for a free thread.

You should not be allowed to do this.

Better contributors documentation.
What is expected when contributing? Tests? Docs (if so how detailed, etc)?

Link from readme.md to contributing section.

related to issue #11

Each experiment and system running can have a confusion matrix for the classifications of each architectural module. This would give a nice overview of the fail data.

Take a look at how the manual mapping works and if/how it should be improved reported. I.e should the manual mapping correct erroneous automatic mappings? how will this affect the precision/recall metrics? Maybe the manual mapping should evolve to something more elaborate where different styles of manual mapping should be available. There are a number of issues to take into consideration:

• no correction vs. correction of automatic mapping fails
• how many manual mappings should be suggested for each iteration 5, 10, 15, 20, big bang?
• other automatic ways to limit the automatic mappings? HuGMe already has this...
• what should be counted as a good suggestion for a manual map? Perfect or correct answer over the median (as done in hugme)
• how should the precision and recall metrics be calculated?
• should the manual mapping always map an entity or should we handle rejected suggestions (which can be used to keep track of things)

In branch physical_dependencies the physical dependencies are messing with the coupling and fan metric calculations.

Likely such dependencies should not be counted in the metrics.

It would be good to have a visualization of the architectures and the base truth mappings.

In the original paper, the relations had different weights when calculating the final attractions. We should add support for using this in the experiments and in the mapper itself.

Hi

From openjournals/joss-reviews#2791

Just wondering if there are any plans to document how others can contribute to s4rdm3x? Related to the following topic in the review process

Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Or maybe there's something already in the docs that I've missed?

Thanks!

Some parts could really use a help text to explain what the parameter/setting actually means.

Using the hierarchical names of packages and files seems to work quite well for java projects. This could be utilized as both a simple naming classifier and as a boot-strapper for more complex classifiers to construct an initial set.

Hi @tobias-dv-lnu ,

I'm following the installation instructions, and it looks like the latest release on GH is missing a ZIP that's present in the other two? I'm downloading a src file, but not sure if it will have the jars I need to keep following the docs?

Related to openjournals/joss-reviews#2791

Thanks
Bruno

From openjournals/joss-reviews#2791

I'm getting the following when trying to load the sample experiment.

$ ~/Development/java/jdk-11.0.2/bin/java -jar v3xt.jar 
Exception when attempting to load/save:/home/kinow/Downloads/1.1/experiment.xml
java.io.IOException: Could not read System File: data\systems\JabRef\3.7\jabref-3_7.sysmdl
java.io.IOException: Could not read System File: data\systems\JabRef\3.7\jabref-3_7.sysmdl
	at se.lnu.siq.s4rdm3x.experiments.system.FileBased.<init>(FileBased.java:32)
	at se.lnu.siq.s4rdm3x.experiments.ExperimentXMLPersistence.elementToRunner(ExperimentXMLPersistence.java:149)
	at se.lnu.siq.s4rdm3x.experiments.ExperimentXMLPersistence.loadExperimentRunners(ExperimentXMLPersistence.java:74)
	at experimenting.ExperimentsView.doSaveButtons(ExperimentsView.java:225)
	at experimenting.ExperimentsView.doView(ExperimentsView.java:116)
	at Main.mainLoop(Main.java:181)
	at Main.lambda$run$0(Main.java:144)
	at uno.glfw.GlfwWindow.loop(GlfwWindow.kt:654)
	at Main.run(Main.java:135)
	at Main.main(Main.java:54)

Any idea what I got wrong?

The physical relations between files are actually missing. We could add relations reflecting this i.e:

pysical_horizontal: between files in the same directory
pysical_vertical: for files in the same parent-child directory

as folder structure is often an important part of the mapping there is a fair chance that this will improve the performance of both CDA and HuGMe