[kepler-dev] Re: sampling

[Efrat Jaeger]

The browserUI actor can probably handle this using the XSLT actor in front
of it (with a desired xsl file). It can be viewed in the attached example
(you'll need to change the 'xslt file path' parameter).

Efrat

----- Original Message ----- 
From: "Shawn Bowers" <bowers at sdsc.edu>
To: "Chad Berkley" <berkley at nceas.ucsb.edu>
Cc: "Deana Pennington" <dpennington at lternet.edu>;
<kepler-dev at ecoinformatics.org>
Sent: Wednesday, May 26, 2004 11:23 AM
Subject: Re: [kepler-dev] Re: sampling


>
>
> Chad Berkley wrote:
> > Hi Deana,
> >
> > See my comments below:
> >
>
> > I've been tossing this idea of stopping the execution to ask for input
> > around in my head since the SEV meeting.  I haven't really come up with
> > a good solution other than writing an extension to the pause actor that
> > allows an input dialog to be popped up.  How to configure that dialog or
> > get the actual information you need is a tough question since I'd like
> > to make it generic enough to work with workflows other than GARP.
> > Edward or Christopher, do you have any examples of workflows that stop
> > execution and ask users for input then continue executing based on that
> > input?  I haven't seen any.  Does anyone have any good ideas on how this
> > could be done generically?
> >
> > The flow as I see it is:
> > 1) execution is paused
> > 2) a dialog that is partially preconfigured at design-time and fully
> > configured at run-time is presented to the user
> > 3) the user makes a choice, altering the exec-time parameters of the
> > rest of the workflow
>
> Isn't this what the "browser" actor does -- the one that Kai, Efrat, and
> Ilkay worked on?
>
>
> shawn
>
>
> >
> > Note that in 2, the run-time configuration may include such things as
> > dialog widget configuration with run-time produced data (e.g. populating
> > a list box with a run-time data stream).  The design-time configuration
> > would include issues such as choosing the input/output ports and
> > configuring what the logic of the dialog is (this may be tricky).
> >
> > I think this is probably a necessary bit of functionality since I have
> > seen a couple different eco workflows prototypes that want to do this.
> >
> > comments?
> >
> > chad
> >
> >>
> >> Deana
> >>
> >>
> >> Chad Berkley wrote:
> >>
> >>> Hi Deana,
> >>>
> >>> I was going to start working on the sampling actor for garp.  could
you
> >>> refresh my memory as to how to that should work.  I have the inputs as
> >>> a species and a scaling metric and the outputs as the intrinsic and
> >>> extrinsic data.  aren't there different sampling techniques?  I'd like
> >>> to build one generic sampling actor that can use one of a number of
> >>> different techniques.  I'm on IRC now if you want to chat about this
in
> >>> real-time.
> >>>
> >>> thanks,
> >>> chad
> >
> >
> > _______________________________________________
> > kepler-dev mailing list
> > kepler-dev at ecoinformatics.org
> > http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
>
> _______________________________________________
> kepler-dev mailing list
> kepler-dev at ecoinformatics.org
> http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Selection.xml
Type: text/xml
Size: 7647 bytes
Desc: not available
Url : http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/kepler-dev/attachments/20040526/4d241c56/Selection.xml