[#TAV-328] Inconsistent data names for LogBook. - myGrid

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 1.5
Component/s: Provenance, Provenance Browser
Labels:
None

Description

The name of the workflow outputs is not consistent:
sometimes the name of the output of the linked processor is used instead.
I noticed this running Paul Fisher's "Pathways and Gene annotations for QTL Phenotype", where several outputs, where wrong.
I could reproduce the problem with "Demonstration of Configurable Iteration" where output (lowercase) was picked instead of "Output" (uppercase).

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Daniele Turi added a comment - 2006-12-13 13:18

Further analysis shows that the problem only occurs when log level "not iterations" is chosen.

Show

Daniele Turi added a comment - 2006-12-13 13:18 Further analysis shows that the problem only occurs when log level "not iterations" is chosen.

Hide

Permalink

Daniele Turi added a comment - 2006-12-13 13:20

Previous comment wrong: on windows I get the same problem selecting "everything" log level too.

Show

Daniele Turi added a comment - 2006-12-13 13:20 Previous comment wrong: on windows I get the same problem selecting "everything" log level too.

Hide

Permalink

Daniele Turi added a comment - 2006-12-14 11:16

The problem was in uk.org.mygrid.logbook.ui.LogBookUIModel.getWorkflowOutputs(WorkflowRun):
it was always get the first value instead of checking whether the output name corresponded to a workflow instead of a processor.

Show

Daniele Turi added a comment - 2006-12-14 11:16 The problem was in uk.org.mygrid.logbook.ui.LogBookUIModel.getWorkflowOutputs(WorkflowRun): it was always get the first value instead of checking whether the output name corresponded to a workflow instead of a processor.

Hide

Permalink

Daniele Turi added a comment - 2007-04-23 15:58

There are still inconsistencies for data names: the intermediate inputs of getComicStrip in the Dilbert workflow are both named url, instead of one base and another url.

Show

Daniele Turi added a comment - 2007-04-23 15:58 There are still inconsistencies for data names: the intermediate inputs of getComicStrip in the Dilbert workflow are both named url, instead of one base and another url.

Hide

Permalink

Daniele Turi added a comment - 2007-04-25 14:38

Fixed using essentially the same fix as workflow outputs: checking whether the data name contains the processRun name.

Show

Daniele Turi added a comment - 2007-04-25 14:38 Fixed using essentially the same fix as workflow outputs: checking whether the data name contains the processRun name.

People

Assignee:

Daniele Turi

Reporter:

Daniele Turi

Vote (0)

Watch (0)

Dates

Created:

2006-12-13 12:55

Updated:

2007-04-25 14:38

Resolved:

2007-04-25 14:38