search

genericworkflownodes / GenericKnimeNodes

Base package for GenericKnimeNodes
https://github.com/genericworkflownodes/GenericKnimeNodes
Other
15 stars 16 forks source link

Updating an old workflow my result in changed output types due to encoding as port number #105

Open timosachsenberg opened 9 years ago

timosachsenberg commented 9 years ago

@aiche addition to our phone call: 2015-05-22 10:15:58,712 WARN KNIME-Worker-0 FeatureLinkerUnlabeledQT : Invalid MIMEtype at port number 0 : has extension: [application/x-mzml]; expected on of:[[featurexml, consensusxml]]

jpfeuffer commented 8 years ago

I have encountered the problem, too. Do you still remember what you came up with? What is encoded as port number?

timosachsenberg commented 8 years ago

IIRC connections are between ports identified by port numbers (not e.g. by names). So introducing a new port may chance the port numbers and lead to incompatible workflows.

timosachsenberg commented 8 years ago

e.g. after updating the mzTabReader node to the new version changed Port / Description 0 The Metadata Section of the mzTab file. 1 The Small Molecule Section of the mzTab file.

To: 0 The Metadata Section of the mzTab file. 1 The Protein Section of the mzTab file. 2 The Peptide Section of the mzTab file. 3 The PSM Section of the mzTab file. 4 The Small Molecule Section of the mzTab file.

With prt 1 being also connected in the updated version (though now the SMS section is port 4)