Miss behaviour with Metrics operations

[jmhorcas]

Describe the bug
The Metrics operations called from a specific plugin (e.g., FMMetrics from fm_metamodel) returns all metrics from all plugins instead of only those metrics from that specific plugin.

To Reproduce
Steps to reproduce the behavior:

1. Import the metric operation of a specific plugin:

from flamapy.metamodels.fm_metamodel.operations import FMMetrics # for FM
from flamapy.metamodels.bdd_metamodel.operations import BDDMetrics # for BDDs

2. Execute the operation:

fm_metrics = FMMetrics().execute(fm_model).get_result()
bdd_metrics = BDDMetrics().execute(fm_model).get_result()  # Another issue here? "execute" expects a FM object, but a BDD object should be expected.

3. See error, both calls returns the same set of metrics (internally, the call to FMMetrics is calling all Metrics operations from all plugins, and the same for the BDDMetrics.
   fm_metrics == bdd_metrics # True

Expected behavior
IMHO, each Metric operation should return only the metrics of its plugin, while the metaoperation in flamapy_fw (the core) should return all metrics from all plugins.

The "execute" operation in the BDD plugin should accept a BDD model object instead of a FM object for consistency with all the rest of operations in the plugin. But I understand that Metrics is a special operation and it has been developed as it on purpose.

Desktop (please complete the following information):

• OS: Linux Mint

[jagalindo]

This is a related issue #122

Describe the bug
The Metric operation is not able to find subclasses of a plugin if the plugin has not been imported from anyway in the application.
The same occurs with the transformations: The Metric operation is not able to find a transformation if there is not any import of such transformation in the code of your application. For instance, Metric operation won't find PySAT to FM if in your code you never import the PySAT2FM transformation in any part.

[jagalindo]

We will see how to address that issue, but take into account that that's not the intended way of using the framework. Rather, to use the discover metamodel and let the fw identify the transformation chains. This is a very advanced ussage not yet supported.

[jagalindo]

This would be a feat request rather than a bug

[jmhorcas]

I agree this should be an enhancement.
The problem with the current behaviour is that the Metric operation returns duplicate metrics (those that are defined in more than one plugin).