LIGO Support Ticket 4015
Ticket Information
Number: support 4015
User: dabrown@physics.syr.edu
Email: deelman__AT__ISI.EDU,skoranda__AT__gravity.phys.uwm.edu,anderson__AT__ligo.caltech.edu,vahi__AT__isi.edu,gmehta__AT__isi.edu,deelman__AT__isi.edu,vahi__AT__ISI.EDU,gmehta__AT__ISI.EDU
Status: open
Assigned To: wenger
CC: Ewa Deelman <deelman__AT__ISI.EDU>, Miron Livny <miron__AT__cs.wisc.edu>,
Scott Koranda <skoranda__AT__gravity.phys.uwm.edu>, Stuart Anderson
<anderson__AT__ligo.caltech.edu>
From: Duncan Brown <dabrown__AT__physics.syr.edu>
Subject: LIGO: request to allow condor_dagman to read DAX syntax
Date: Mon, 30 Jun 2008 11:03:37 -0400
To: condor-support response tracking system <condor-support__AT__cs.wisc.edu>
X-Scanner: InterScan AntiVirus for Sendmail
X-Seen-BY: mailfromd 4.1 granite.cs.wisc.edu
Hi all,
LIGO currently writes workflows in two formats, condor_dagman +
submit file format and the Pegasus XML DAX format. We discussed at
the Milwaukee grid workshop a plan to allow condor_dagman to read the
DAX format, so LIGO can move to generating the DAX format for all
workflows.
I'd like to put in a request to make this transition in dagman.
Cheers,
Duncan.
--
Duncan Brown Room 263-1, Department of Physics,
Assistant Professor of Physics Syracuse University, NY 13244, USA
Phone: (315) 443 5993 http://www.gravity.phy.syr.edu/~duncan
===========================================================================
Date of creation: Mon Jun 30 10:07:21 2008 (1214838453)
Subject: Actions
Assigned to psilord by psilord
===========================================================================
Date of actions: Wed Jul 2 14:39:03 2008 (1215027543)
Subject: Actions
Assigned to wenger by psilord
===========================================================================
Date of actions: Wed Jul 2 14:44:52 2008 (1215027892)
Date: Wed, 2 Jul 2008 14:52:15 -0500 (CDT)
From: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
To: psilord <condor-support__AT__cs.wisc.edu>
CC: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
Subject: Re: [condor-support #4015] LIGO: request to allow condor_dagman
to read DAX syntax
Duncan,
> LIGO currently writes workflows in two formats, condor_dagman +
> submit file format and the Pegasus XML DAX format. We discussed at
> the Milwaukee grid workshop a plan to allow condor_dagman to read the
> DAX format, so LIGO can move to generating the DAX format for all
> workflows.
>
> I'd like to put in a request to make this transition in dagman.
Is there some reason you can't just run pegasus-plan on the DAX files?
Unless I'm not understanding exactly what you're asking for, supporting
DAX files in DAGMan seems problematic. Either we'd have to essentially
re-create Pegasus, or only support a small subset of the Pegasus
functionality.
Can you give us some more info about what sort of use cases are behind
this request?
Kent Wenger
Condor Team
===========================================================================
Date mail was appended: Wed Jul 2 14:52:27 2008 (1215028348)
CC: deelman__AT__ISI.EDU, skoranda__AT__gravity.phys.uwm.edu, anderson__AT__ligo.caltech.edu
From: Duncan Brown <dabrown__AT__physics.syr.edu>
Subject: Re: [condor-support #4015] LIGO: request to allow condor_dagman
to read DAX syntax
Date: Wed, 2 Jul 2008 16:01:18 -0400
To: condor-support__AT__cs.wisc.edu
X-Scanner: InterScan AntiVirus for Sendmail
X-Seen-BY: mailfromd 4.1 gypsum.cs.wisc.edu
Hi Kent,
We're not asking for the Pegasus functionality in DAGman*, just
unifying the syntax with which one describes the workflow. Right now
we have two languages: a condor dag file, coupled with a bunch
of .sub files, and a DAX. The DAX language is a superset of the
condor dag+sub language, since it describes the jobs, the arguments,
the relationship between nodes, etc.
What we'd like is to be able to write a DAX and have condor_dagman
run it as if it was just running the same workflow from dag+sub
files. If we can do this, we can work our way towards things like
just-in-time planning and other longer term things.
Scott, have I captured this discussion correctly?
Cheers,
Duncan.
*yet :) Although this was discussed in the pega-dag-man long range
discussion by Miron and Ewa at the UWM workshop.
On Jul 2, 2008, at 3:52 PM, condor-support response tracking system
wrote:
> Duncan,
>
>> LIGO currently writes workflows in two formats, condor_dagman +
>> submit file format and the Pegasus XML DAX format. We discussed at
>> the Milwaukee grid workshop a plan to allow condor_dagman to read the
>> DAX format, so LIGO can move to generating the DAX format for all
>> workflows.
>>
>> I'd like to put in a request to make this transition in dagman.
>
> Is there some reason you can't just run pegasus-plan on the DAX files?
>
> Unless I'm not understanding exactly what you're asking for,
> supporting
> DAX files in DAGMan seems problematic. Either we'd have to
> essentially
> re-create Pegasus, or only support a small subset of the Pegasus
> functionality.
>
> Can you give us some more info about what sort of use cases are behind
> this request?
>
> Kent Wenger
> Condor Team
>
>
> ========================================
> MESSAGE INFORMATION
> ========================================
> * From: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
> * Ticket Email List: dabrown__AT__physics.syr.edu,
> deelman__AT__ISI.EDU,skoranda__AT__gravity.phys.uwm.edu,anderson__AT__ligo.caltech.ed
> u
--
Duncan Brown Room 263-1, Department of Physics,
Assistant Professor of Physics Syracuse University, NY 13244, USA
Phone: (315) 443 5993 http://www.gravity.phy.syr.edu/~duncan
===========================================================================
Date mail was appended: Wed Jul 2 15:01:18 2008 (1215028879)
Date: Wed, 2 Jul 2008 16:19:33 -0500 (CDT)
From: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
To: condor-support response tracking system <condor-support__AT__cs.wisc.edu>
CC: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
Subject: Re: [condor-support #4015] LIGO: request to allow condor_dagman
to read DAX syntax
Duncan,
> We're not asking for the Pegasus functionality in DAGman*, just
> unifying the syntax with which one describes the workflow. Right now
> we have two languages: a condor dag file, coupled with a bunch
> of .sub files, and a DAX. The DAX language is a superset of the
> condor dag+sub language, since it describes the jobs, the arguments,
> the relationship between nodes, etc.
Well, there are details at the submit file level that are not exposed in
the DAX language, but they are probably not important in most cases.
> What we'd like is to be able to write a DAX and have condor_dagman
> run it as if it was just running the same workflow from dag+sub
> files. If we can do this, we can work our way towards things like
> just-in-time planning and other longer term things.
>
> Scott, have I captured this discussion correctly?
Hmm, sounds like I need to talk to Miron and get his ideas about this.
At any rate, I don't think it will happen in the real near future. If
nothing else, we would need to define exactly how it would work.
Kent Wenger
Condor Team
===========================================================================
Date mail was appended: Wed Jul 2 16:24:21 2008 (1215033862)
CC: deelman__AT__ISI.EDU, skoranda__AT__gravity.phys.uwm.edu, anderson__AT__ligo.caltech.edu
From: Duncan Brown <dabrown__AT__physics.syr.edu>
Subject: Re: [condor-support #4015] LIGO: request to allow condor_dagman
to read DAX syntax
Date: Thu, 3 Jul 2008 09:04:20 -0400
To: condor-support__AT__cs.wisc.edu
X-Scanner: InterScan AntiVirus for Sendmail
X-Seen-BY: mailfromd 4.1 granite.cs.wisc.edu
Hi Kent,
Thanks. This certainly isn't something we need next week, but I'd
like to get the ball rolling in this direction.
Cheers,
Duncan.
On Jul 2, 2008, at 5:24 PM, condor-support response tracking system
wrote:
> Duncan,
>
>> We're not asking for the Pegasus functionality in DAGman*, just
>> unifying the syntax with which one describes the workflow. Right now
>> we have two languages: a condor dag file, coupled with a bunch
>> of .sub files, and a DAX. The DAX language is a superset of the
>> condor dag+sub language, since it describes the jobs, the arguments,
>> the relationship between nodes, etc.
>
> Well, there are details at the submit file level that are not
> exposed in
> the DAX language, but they are probably not important in most cases.
>
>> What we'd like is to be able to write a DAX and have condor_dagman
>> run it as if it was just running the same workflow from dag+sub
>> files. If we can do this, we can work our way towards things like
>> just-in-time planning and other longer term things.
>>
>> Scott, have I captured this discussion correctly?
>
> Hmm, sounds like I need to talk to Miron and get his ideas about this.
>
> At any rate, I don't think it will happen in the real near future. If
> nothing else, we would need to define exactly how it would work.
>
> Kent Wenger
> Condor Team
>
>
> ========================================
> MESSAGE INFORMATION
> ========================================
> * From: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
> * Ticket Email List: dabrown__AT__physics.syr.edu,
> deelman__AT__ISI.EDU,skoranda__AT__gravity.phys.uwm.edu,anderson__AT__ligo.caltech.ed
> u
--
Duncan Brown Room 263-1, Department of Physics,
Assistant Professor of Physics Syracuse University, NY 13244, USA
Phone: (315) 443 5993 http://www.gravity.phy.syr.edu/~duncan
===========================================================================
Date mail was appended: Thu Jul 3 8:04:21 2008 (1215090261)
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
Subject: RE: [condor-support #4015] LIGO: request to allow condor_dagman
to read DAX syntax
Date: Thu, 3 Jul 2008 07:16:33 -0700
X-MS-Has-Attach:
X-MS-Tnef-Correlator:
Thread-Topic: [condor-support #4015] LIGO: request to allow condor_dagman
to read DAX syntax
Thread-Index: Acjcigm00tT32HYzQmWRBjFAJb3pnwAjUKAw
From: "Ewa Deelman" <deelman__AT__isi.edu>
To: <condor-support__AT__cs.wisc.edu>, <dabrown__AT__physics.syr.edu>
CC: <skoranda__AT__gravity.phys.uwm.edu>, <anderson__AT__ligo.caltech.edu>,
"Karan Vahi" <vahi__AT__isi.edu>,
"Gaurang Mehta" <gmehta__AT__isi.edu>
X-Seen-BY: mailfromd 4.1 gypsum.cs.wisc.edu
X-MIME-Autoconverted: from quoted-printable to 8bit by chopin.cs.wisc.edu
id m63EGxnG027882
The other thing, which is probably easier would be to have Pegasus take
in a DAG and invoke DAGMan in that case.
-Ewa
> -----Original Message-----
> From: condor-support response tracking system [mailto:condor-
> support__AT__cs.wisc.edu]
> Sent: Wednesday, July 02, 2008 2:24 PM
> To: dabrown__AT__physics.syr.edu
> Cc: Ewa Deelman; skoranda__AT__gravity.phys.uwm.edu;
anderson__AT__ligo.caltech.edu
> Subject: Re: [condor-support #4015] LIGO: request to allow
condor_dagman
> to read DAX syntax
>
> Duncan,
>
> > We're not asking for the Pegasus functionality in DAGman*, just
> > unifying the syntax with which one describes the workflow. Right now
> > we have two languages: a condor dag file, coupled with a bunch
> > of .sub files, and a DAX. The DAX language is a superset of the
> > condor dag+sub language, since it describes the jobs, the arguments,
> > the relationship between nodes, etc.
>
> Well, there are details at the submit file level that are not exposed
in
> the DAX language, but they are probably not important in most cases.
>
> > What we'd like is to be able to write a DAX and have condor_dagman
> > run it as if it was just running the same workflow from dag+sub
> > files. If we can do this, we can work our way towards things like
> > just-in-time planning and other longer term things.
> >
> > Scott, have I captured this discussion correctly?
>
> Hmm, sounds like I need to talk to Miron and get his ideas about this.
>
> At any rate, I don't think it will happen in the real near future. If
> nothing else, we would need to define exactly how it would work.
>
> Kent Wenger
> Condor Team
>
>
> ========================================
> MESSAGE INFORMATION
> ========================================
> * From: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
> * Ticket Email List: dabrown__AT__physics.syr.edu,
>
deelman__AT__ISI.EDU,skoranda__AT__gravity.phys.uwm.edu,anderson__AT__ligo.caltech.edu
===========================================================================
Date mail was appended: Thu Jul 3 9:17:04 2008 (1215094626)
CC: <condor-support__AT__cs.wisc.edu>, <skoranda__AT__gravity.phys.uwm.edu>,
<anderson__AT__ligo.caltech.edu>,
"Karan Vahi" <vahi__AT__isi.edu>,
"Gaurang Mehta" <gmehta__AT__isi.edu>
From: Duncan Brown <dabrown__AT__physics.syr.edu>
Subject: Re: [condor-support #4015] LIGO: request to allow condor_dagman
to read DAX syntax
Date: Mon, 7 Jul 2008 10:10:32 -0400
To: Ewa Deelman <deelman__AT__isi.edu>
X-Scanner: InterScan AntiVirus for Sendmail
X-Seen-BY: mailfromd 4.1 granite.cs.wisc.edu
Hi Ewa,
I don't think we want to go this way. I'd like us to move towards a
unified language for describing workflows, if possible.
Cheers,
Duncan.
On Jul 3, 2008, at 10:16 AM, Ewa Deelman wrote:
> The other thing, which is probably easier would be to have Pegasus
> take
> in a DAG and invoke DAGMan in that case.
>
> -Ewa
>
>
>> -----Original Message-----
>> From: condor-support response tracking system [mailto:condor-
>> support__AT__cs.wisc.edu]
>> Sent: Wednesday, July 02, 2008 2:24 PM
>> To: dabrown__AT__physics.syr.edu
>> Cc: Ewa Deelman; skoranda__AT__gravity.phys.uwm.edu;
> anderson__AT__ligo.caltech.edu
>> Subject: Re: [condor-support #4015] LIGO: request to allow
> condor_dagman
>> to read DAX syntax
>>
>> Duncan,
>>
>>> We're not asking for the Pegasus functionality in DAGman*, just
>>> unifying the syntax with which one describes the workflow. Right now
>>> we have two languages: a condor dag file, coupled with a bunch
>>> of .sub files, and a DAX. The DAX language is a superset of the
>>> condor dag+sub language, since it describes the jobs, the arguments,
>>> the relationship between nodes, etc.
>>
>> Well, there are details at the submit file level that are not exposed
> in
>> the DAX language, but they are probably not important in most cases.
>>
>>> What we'd like is to be able to write a DAX and have condor_dagman
>>> run it as if it was just running the same workflow from dag+sub
>>> files. If we can do this, we can work our way towards things like
>>> just-in-time planning and other longer term things.
>>>
>>> Scott, have I captured this discussion correctly?
>>
>> Hmm, sounds like I need to talk to Miron and get his ideas about
>> this.
>>
>> At any rate, I don't think it will happen in the real near
>> future. If
>> nothing else, we would need to define exactly how it would work.
>>
>> Kent Wenger
>> Condor Team
>>
>>
>> ========================================
>> MESSAGE INFORMATION
>> ========================================
>> * From: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
>> * Ticket Email List: dabrown__AT__physics.syr.edu,
>>
> deelman__AT__ISI.EDU,skoranda__AT__gravity.phys.uwm.edu,anderson__AT__ligo.caltech.ed
> u
>
--
Duncan Brown Room 263-1, Department of Physics,
Assistant Professor of Physics Syracuse University, NY 13244, USA
Phone: (315) 443 5993 http://www.gravity.phy.syr.edu/~duncan
===========================================================================
Date mail was appended: Mon Jul 7 9:11:40 2008 (1215439901)
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
Subject: RE: [condor-support #4015] LIGO: request to allow condor_dagman
to read DAX syntax
Date: Mon, 7 Jul 2008 07:29:10 -0700
X-MS-Has-Attach:
X-MS-Tnef-Correlator:
Thread-Topic: [condor-support #4015] LIGO: request to allow condor_dagman
to read DAX syntax
Thread-Index: AcjgO27HmuuDRhDsTYSLKP6aHRGH9gAAk+/Q
From: "Ewa Deelman" <deelman__AT__isi.edu>
To: <condor-support__AT__cs.wisc.edu>
X-Seen-BY: mailfromd 4.1 granite.cs.wisc.edu
X-MIME-Autoconverted: from quoted-printable to 8bit by chopin.cs.wisc.edu
id m67ETLxs024387
Hi Duncan,
Can we have a call about this sometime tomorrow afternoon?
Thanks,
_Ewa
> -----Original Message-----
> From: condor-support response tracking system [mailto:condor-
> support__AT__cs.wisc.edu]
> Sent: Monday, July 07, 2008 7:12 AM
> To: Ewa Deelman
> Subject: Re: [condor-support #4015] LIGO: request to allow
condor_dagman
> to read DAX syntax
>
> Hi Ewa,
>
> I don't think we want to go this way. I'd like us to move towards a
> unified language for describing workflows, if possible.
>
> Cheers,
> Duncan.
>
> On Jul 3, 2008, at 10:16 AM, Ewa Deelman wrote:
>
> > The other thing, which is probably easier would be to have Pegasus
> > take
> > in a DAG and invoke DAGMan in that case.
> >
> > -Ewa
> >
> >
> >> -----Original Message-----
> >> From: condor-support response tracking system [mailto:condor-
> >> support__AT__cs.wisc.edu]
> >> Sent: Wednesday, July 02, 2008 2:24 PM
> >> To: dabrown__AT__physics.syr.edu
> >> Cc: Ewa Deelman; skoranda__AT__gravity.phys.uwm.edu;
> > anderson__AT__ligo.caltech.edu
> >> Subject: Re: [condor-support #4015] LIGO: request to allow
> > condor_dagman
> >> to read DAX syntax
> >>
> >> Duncan,
> >>
> >>> We're not asking for the Pegasus functionality in DAGman*, just
> >>> unifying the syntax with which one describes the workflow. Right
now
> >>> we have two languages: a condor dag file, coupled with a bunch
> >>> of .sub files, and a DAX. The DAX language is a superset of the
> >>> condor dag+sub language, since it describes the jobs, the
arguments,
> >>> the relationship between nodes, etc.
> >>
> >> Well, there are details at the submit file level that are not
exposed
> > in
> >> the DAX language, but they are probably not important in most
cases.
> >>
> >>> What we'd like is to be able to write a DAX and have condor_dagman
> >>> run it as if it was just running the same workflow from dag+sub
> >>> files. If we can do this, we can work our way towards things like
> >>> just-in-time planning and other longer term things.
> >>>
> >>> Scott, have I captured this discussion correctly?
> >>
> >> Hmm, sounds like I need to talk to Miron and get his ideas about
> >> this.
> >>
> >> At any rate, I don't think it will happen in the real near
> >> future. If
> >> nothing else, we would need to define exactly how it would work.
> >>
> >> Kent Wenger
> >> Condor Team
> >>
> >>
> >> ========================================
> >> MESSAGE INFORMATION
> >> ========================================
> >> * From: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
> >> * Ticket Email List: dabrown__AT__physics.syr.edu,
> >>
> >
deelman__AT__ISI.EDU,skoranda__AT__gravity.phys.uwm.edu,anderson__AT__ligo.caltech.ed
> > u
> >
>
> --
>
> Duncan Brown Room 263-1, Department of
Physics,
> Assistant Professor of Physics Syracuse University, NY 13244,
USA
> Phone: (315) 443 5993
http://www.gravity.phy.syr.edu/~duncan
>
>
>
>
> ========================================
> MESSAGE INFORMATION
> ========================================
> * From: Duncan Brown <dabrown__AT__physics.syr.edu>
> * Ticket Email List: dabrown__AT__physics.syr.edu,
>
deelman__AT__ISI.EDU,skoranda__AT__gravity.phys.uwm.edu,anderson__AT__ligo.caltech.edu,
va
> hi__AT__isi.edu,gmehta__AT__isi.edu,deelman__AT__isi.edu
===========================================================================
Date mail was appended: Mon Jul 7 9:29:28 2008 (1215440970)
Date: Tue, 8 Jul 2008 17:59:19 -0500 (CDT)
From: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
To: condor-support response tracking system <condor-support__AT__cs.wisc.edu>
CC: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
Subject: Re: [condor-support #4015] LIGO: request to allow condor_dagman
to read DAX syntax
On Mon, 7 Jul 2008, condor-support response tracking system wrote:
> Can we have a call about this sometime tomorrow afternoon?
Ah, I was on vacation yesterday and just saw this, so no phone call for me
today. I could do tomorrow or Thursday, though, if you want me to be
involved.
Kent Wenger
Condor Team
===========================================================================
Date mail was appended: Tue Jul 8 18:03:50 2008 (1215558231)
Date: Tue, 8 Jul 2008 16:21:06 -0700
From: Stuart Anderson <anderson__AT__ligo.caltech.edu>
To: condor-support response tracking system <condor-support__AT__cs.wisc.edu>
CC: dabrown__AT__physics.syr.edu, deelman__AT__ISI.EDU,
skoranda__AT__gravity.phys.uwm.edu, vahi__AT__ISI.EDU, gmehta__AT__ISI.EDU
Subject: Re: [condor-support #4015] LIGO: request to allow condor_dagman
to read DAX syntax
X-Seen-BY: mailfromd 4.1 granite.cs.wisc.edu
The next joint LIGO-Condor call is this Friday (July 18) at 10AM Pacific.
If you want to have a discussion on this topic in that meeting that would
be fine with me.
Thanks.
On Tue, Jul 08, 2008 at 06:03:50PM -0500, condor-support response tracking system wrote:
> On Mon, 7 Jul 2008, condor-support response tracking system wrote:
>
> > Can we have a call about this sometime tomorrow afternoon?
>
> Ah, I was on vacation yesterday and just saw this, so no phone call for me
> today. I could do tomorrow or Thursday, though, if you want me to be
> involved.
>
> Kent Wenger
> Condor Team
>
>
> ========================================
> MESSAGE INFORMATION
> ========================================
> * From: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
> * Ticket Email List: dabrown__AT__physics.syr.edu, deelman__AT__ISI.EDU,skoranda__AT__gravity.phys.uwm.edu,anderson__AT__ligo.caltech.edu,vahi__AT__isi.edu,gmehta__AT__isi.edu,deelman__AT__isi.edu
>
--
Stuart Anderson anderson__AT__ligo.caltech.edu
http://www.ligo.caltech.edu/~anderson
===========================================================================
Date mail was appended: Tue Jul 8 18:21:17 2008 (1215559277)
CC: condor-support response tracking system <condor-support__AT__cs.wisc.edu>,
deelman__AT__ISI.EDU, skoranda__AT__gravity.phys.uwm.edu, vahi__AT__ISI.EDU,
gmehta__AT__ISI.EDU
From: Duncan Brown <dabrown__AT__physics.syr.edu>
Subject: Re: [condor-support #4015] LIGO: request to allow condor_dagman
to read DAX syntax
Date: Tue, 8 Jul 2008 19:45:01 -0400
To: Stuart Anderson <anderson__AT__ligo.caltech.edu>
X-Scanner: InterScan AntiVirus for Sendmail
X-Seen-BY: mailfromd 4.1 silica.cs.wisc.edu
Hi Stuart,
Ewa and I had a brief conversation about this today, so I can
summarize this in the call on Friday.
Cheers,
Duncan.
On Jul 8, 2008, at 7:21 PM, Stuart Anderson wrote:
> The next joint LIGO-Condor call is this Friday (July 18) at 10AM
> Pacific.
> If you want to have a discussion on this topic in that meeting that
> would
> be fine with me.
>
> Thanks.
>
> On Tue, Jul 08, 2008 at 06:03:50PM -0500, condor-support response
> tracking system wrote:
>> On Mon, 7 Jul 2008, condor-support response tracking system wrote:
>>
>>> Can we have a call about this sometime tomorrow afternoon?
>>
>> Ah, I was on vacation yesterday and just saw this, so no phone
>> call for me
>> today. I could do tomorrow or Thursday, though, if you want me to be
>> involved.
>>
>> Kent Wenger
>> Condor Team
>>
>>
>> ========================================
>> MESSAGE INFORMATION
>> ========================================
>> * From: "R. Kent Wenger" <wenger__AT__cs.wisc.edu>
>> * Ticket Email List: dabrown__AT__physics.syr.edu,
>> deelman__AT__ISI.EDU,skoranda__AT__gravity.phys.uwm.edu,anderson__AT__ligo.caltech.e
>> du,vahi__AT__isi.edu,gmehta__AT__isi.edu,deelman__AT__isi.edu
>>
>
> --
> Stuart Anderson anderson__AT__ligo.caltech.edu
> http://www.ligo.caltech.edu/~anderson
--
Duncan Brown Room 263-1, Department of Physics,
Assistant Professor of Physics Syracuse University, NY 13244, USA
Phone: (315) 443 5993 http://www.gravity.phy.syr.edu/~duncan
===========================================================================
Date mail was appended: Tue Jul 8 18:45:02 2008 (1215560704)
Subject: Comments added
Todd and/or Kent need to talk to Miron so we can report back to LIGO
about a timeframe for adding a condor_submit_dax as part of our
grant w/ Pegasus.
Comments added by tannenba
===========================================================================
Date comments were added: Fri Jul 18 13:22:06 2008 (1216405452)