Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

[Note that there was no meeting last week; UNIMAN was busy with workshops.]

Attendees

  • Donal Fellows (UNIMAN)
  • Finn Bacall (UNIMAN)
  • Markus Plangg (TUW)
  • Rainer Schmidt (AIT)
  • Michael Kraxner (TUW)
  • Carl Wilson (OPF)

Notes

Started review preparation. General plan is to have:

  1. some slides to show setting of component work within wider SCAPE project
  2. live (but possibly offline) demo
    • Will include looking inside some components
    • Would be nice to illustrate some components based on SCAPE tools (coordinate with PC) and showing multi-step contents too

There was some discussion of the myExperiment query system, including whether results are generated as XML or RDF (old RDF generator is PHP and uses historical data — daily database dumps — for aggregate queries).
New SPARQL query engine will restrict results, only allowing specific types to be returned (workflows, components) and only permitting a user to see the workflows they're permitted to. When not logged in, only public workflows/components will be visible.

Discussed typing of ports (file vs url). Particular case was whether a component might need a directory name, which would be relevant in a PDF to TIFF conversion (directory would hold multiple TIFF images, one per page of input PDF). Was pointed out that the component could produce a list of produced images as an output in this case, and that adding code to a component to allow it to select where to write output files by default would not be difficult (though allowing an override would make a lot of sense).

Actions

From last time

ACT.130307.04 Finn: Allow myExp to tolerate anonymous nodes; mustn't crash!
DONE: No longer crashes. Advanced query work in progress.

ACT.130307.05 Finn: Solution for how to do SCAPE-specific queries for review.
DONE: Use existing query engine

ACT.130307.07 Markus: Use jplyzer as example to create comprehensive CC component. (coordinate with Carl, Johann, TUW)
ONGOING

ACT.130307.11 Alan: Update plugin (0.9?)
DONE

ACT.130307.12 Alan: SCAPE-specific GUI for migration path & parameters
ONGOING

ACT.130314.01 Donal: Ask Sean for assistance with ontology writing
ONGOING

ACT.130314.02 Finn: Create brief feature list of myExperiments regarding components
ONGOING

ACT.130314.03 Markus: Create QA component example
ONGOING

ACT.130314.04 KEEP: Add commandline tool license to toolspec
ONGOING (would be useful to coordinate with wf4ever project team at UNIMAN)

New

ACT.280313.01 Donal: Draft of Component demo for review (DEADLINE: 4/4/13)
ACT.280313.02 Donal: Put example components for jplyzer and imagemagick components in myExp

Current

ACT.130307.07 Markus: Use jplyzer as example to create comprehensive CC component. (coordinate with Carl, Johann, TUW)
ACT.130307.12 Alan: SCAPE-specific GUI for migration path & parameters
ACT.130314.01 Donal: Ask Sean for assistance with ontology writing
ACT.130314.02 Finn: Create brief feature list of myExperiments regarding components
ACT.130314.03 Markus: Create QA component example
ACT.130314.04 KEEP: Add commandline tool license to toolspec
ACT.280313.01 Donal: Draft of Component demo for review (DEADLINE: 4/4/13)
ACT.280313.02 Donal: Put example components for jplyzer and imagemagick components in myExp

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.