[kepler-dev] [Fwd: DDF Director documentation]

Christopher Brooks cxh at eecs.berkeley.edu
Wed Jan 30 16:33:28 PST 2008


Hi Kirsten,
There is a DDF chapter in Volume 3 of the Ptolemy II Design Doc:
http://www.eecs.berkeley.edu/Pubs/TechRpts/2007/EECS-2007-9.html

_Christopher

--------

    
    Hi Dan,
    =20
    Could we please keep the DDF director in the actor tree.  My workflow is
    held together with duct tape and chicken wire and this is the one small
    piece that holds it together.  Norbert recommended that we use this
    director and I don't think that there is any other way to implement what
    we are trying to do without it.  I'm not altogether sure how it works so
    any documentation that could be provided in the future on the DDF
    Director would be really helpful!!
    =20
    Thanks,
    Jared Chase
    
    -------- Original Message --------=20
    Subject: 	[kepler-dev] DDF Director documentation=09
    Date: 	Tue, 29 Jan 2008 14:03:57 -0800=09
    From: 	Dan Higgins <higgins at nceas.ucsb.edu>
    <mailto:higgins at nceas.ucsb.edu> =09
    To: 	Norbert Podhorszki <npodhorszki at ucdavis.edu>
    <mailto:npodhorszki at ucdavis.edu> , Kirsten Menger-Anderson
    <kma500 at gmail.com> <mailto:kma500 at gmail.com> , Kepler-Dev
    <kepler-dev at ecoinformatics.org> <mailto:kepler-dev at ecoinformatics.org> =09
    
    
    
    Hi All,
    
        Currently, Kepler (CVS Head) includes a DDF director. This director
    is not one of the 4 documented in any of the documentation prepared to
    date. Since we are trying to get an rc1 release we have the question of
    
    1) Trying to add documentation in the next few days. This would probably
    require Kirsten to coordinate with Norbert who is the only one with
    experience using the DDF director in Kepler (and apparently has some
    example workflow)
    
    or 2) removing the DDF director from the actor tree. This would remove
    confusion among new user, but leaving it in the compiled code would mean
    that workflows using DDF would still run and the actor could be
    instantiated and added to new workflow by anyone knowing about it. It
    could then be added to the tree when documentation was completed (1.0 ?)
    
    Can we do 1)? or should we go with 2) for rc1?
    
    Dan Higgins
    
    --
    *******************************************************************
    Dan Higgins                                  higgins at nceas.ucsb.edu
    http://www.nceas.ucsb.edu/    Ph: 805-893-5127
    National Center for Ecological Analysis and Synthesis (NCEAS) Marine
    Science Building - Room 3405
    Santa Barbara, CA 93195
    *******************************************************************
    
    _______________________________________________
    Kepler-dev mailing list
    Kepler-dev at ecoinformatics.org
    http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
    
    
    
    ------_=_NextPart_001_01C8639A.0AF4C7A8
    Content-Type: text/html;
    	charset="us-ascii"
    Content-Transfer-Encoding: quoted-printable
    
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    <HTML><HEAD><TITLE>[kepler-dev] DDF Director documentation</TITLE>
    <META http-equiv=3DContent-Type content=3D"text/html; =
    charset=3Dus-ascii">
    <META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
    <BODY text=3D#000000 bgColor=3D#ffffff>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
    size=3D2><SPAN=20
    class=3D376532223-30012008>Hi Dan,</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
    size=3D2><SPAN=20
    class=3D376532223-30012008></SPAN></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
    size=3D2><SPAN=20
    class=3D376532223-30012008>Could we please keep the DDF director in the =
    actor=20
    tree.&nbsp; <SPAN class=3D376532223-30012008>My workflow is held =
    together with=20
    duct tape and chicken wire and this is the one small piece that holds it =
    
    together.&nbsp; </SPAN></SPAN></FONT><FONT face=3DArial color=3D#0000ff =
    size=3D2><SPAN=20
    class=3D376532223-30012008>Norbert recommended that we use this director =
    and I=20
    don't think that there is any other way to implement what we are trying =
    to do=20
    without it.&nbsp; </SPAN></FONT><FONT face=3DArial color=3D#0000ff =
    size=3D2><SPAN=20
    class=3D376532223-30012008>I'm not altogether sure how it works so any=20
    documentation that could be provided in the future on the DDF Director =
    would be=20
    really helpful!!</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
    size=3D2><SPAN=20
    class=3D376532223-30012008></SPAN></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
    size=3D2><SPAN=20
    class=3D376532223-30012008>Thanks,</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
    size=3D2><SPAN=20
    class=3D376532223-30012008>Jared Chase</SPAN></FONT></DIV><FONT =
    face=3DArial=20
    color=3D#0000ff size=3D2></FONT><BR>-------- Original Message --------=20
    <TABLE class=3Dmoz-email-headers-table cellSpacing=3D0 cellPadding=3D0 =
    border=3D0>
      <TBODY>
      <TR>
        <TH vAlign=3Dbaseline noWrap align=3Dright>Subject: </TH>
        <TD>[kepler-dev] DDF Director documentation</TD></TR>
      <TR>
        <TH vAlign=3Dbaseline noWrap align=3Dright>Date: </TH>
        <TD>Tue, 29 Jan 2008 14:03:57 -0800</TD></TR>
      <TR>
        <TH vAlign=3Dbaseline noWrap align=3Dright>From: </TH>
        <TD>Dan Higgins <A class=3Dmoz-txt-link-rfc2396E=20
          =
    href=3D"mailto:higgins at nceas.ucsb.edu">&lt;higgins at nceas.ucsb.edu&gt;</A>=
    </TD></TR>
      <TR>
        <TH vAlign=3Dbaseline noWrap align=3Dright>To: </TH>
        <TD>Norbert Podhorszki <A class=3Dmoz-txt-link-rfc2396E=20
          =
    href=3D"mailto:npodhorszki at ucdavis.edu">&lt;npodhorszki at ucdavis.edu&gt;</=
    A>,=20
          Kirsten Menger-Anderson <A class=3Dmoz-txt-link-rfc2396E=20
          href=3D"mailto:kma500 at gmail.com">&lt;kma500 at gmail.com&gt;</A>, =
    Kepler-Dev <A=20
          class=3Dmoz-txt-link-rfc2396E=20
          =
    href=3D"mailto:kepler-dev at ecoinformatics.org">&lt;kepler-dev at ecoinformati=
    cs.org&gt;</A></TD></TR></TBODY></TABLE><BR><BR>
    <META content=3D"MS Exchange Server version 6.5.7652.24" =
    name=3DGenerator><!-- Converted from text/plain format -->
    <P><FONT size=3D2>Hi All,<BR><BR>&nbsp;&nbsp;&nbsp; Currently, Kepler =
    (CVS Head)=20
    includes a DDF director. This director<BR>is not one of the 4 documented =
    in any=20
    of the documentation prepared to<BR>date. Since we are trying to get an =
    rc1=20
    release we have the question of<BR><BR>1) Trying to add documentation in =
    the=20
    next few days. This would probably<BR>require Kirsten to coordinate with =
    Norbert=20
    who is the only one with<BR>experience using the DDF director in Kepler =
    (and=20
    apparently has some<BR>example workflow)<BR><BR>or 2) removing the DDF =
    director=20
    from the actor tree. This would remove<BR>confusion among new user, but =
    leaving=20
    it in the compiled code would mean<BR>that workflows using DDF would =
    still run=20
    and the actor could be<BR>instantiated and added to new workflow by =
    anyone=20
    knowing about it. It<BR>could then be added to the tree when =
    documentation was=20
    completed (1.0 ?)<BR><BR>Can we do 1)? or should we go with 2) for=20
    rc1?<BR><BR>Dan=20
    Higgins<BR><BR>--<BR>****************************************************=
    ***************<BR>Dan=20
    Higgins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
    nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    <A class=3Dmoz-txt-link-abbreviated=20
    href=3D"mailto:higgins at nceas.ucsb.edu">higgins at nceas.ucsb.edu</A><BR><A=20
    href=3D"http://www.nceas.ucsb.edu/"=20
    moz-do-not-send=3D"true">http://www.nceas.ucsb.edu/</A>&nbsp;&nbsp;&nbsp;=
     Ph:=20
    805-893-5127<BR>National Center for Ecological Analysis and Synthesis =
    (NCEAS)=20
    Marine Science Building - Room 3405<BR>Santa Barbara, CA=20
    93195<BR>****************************************************************=
    ***<BR><BR>_______________________________________________<BR>Kepler-dev =
    
    mailing list<BR><A class=3Dmoz-txt-link-abbreviated=20
    href=3D"mailto:Kepler-dev at ecoinformatics.org">Kepler-dev at ecoinformatics.o=
    rg</A><BR><A=20
    href=3D"http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kep=
    ler-dev"=20
    moz-do-not-send=3D"true">http://mercury.nceas.ucsb.edu/ecoinformatics/mai=
    lman/listinfo/kepler-dev</A><BR></FONT></P></BODY></HTML>
    
    ------_=_NextPart_001_01C8639A.0AF4C7A8--
    
    --===============1627047594==
    Content-Type: text/plain; charset="us-ascii"
    MIME-Version: 1.0
    Content-Transfer-Encoding: 7bit
    Content-Disposition: inline
    
    _______________________________________________
    Kepler-dev mailing list
    Kepler-dev at ecoinformatics.org
    http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
    
    --===============1627047594==--
--------



More information about the Kepler-dev mailing list