From bugzilla-daemon at mcs.anl.gov Sun Jul 1 00:09:12 2007
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sun, 1 Jul 2007 00:09:12 -0500 (CDT)
Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
In-Reply-To:
Message-ID: <20070701050912.2A2BC16505@foxtrot.mcs.anl.gov>
http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=72
------- Comment #7 from iraicu at cs.uchicago.edu 2007-07-01 00:09 -------
(In reply to comment #6)
> (In reply to comment #4)
> > Hi again,
> > Here is an update of yesterday's 244 molecule run. The experiment ran further
> > than before, but it still did not complete. There were 240 molecules that
> > completed successfully (in the previous run, no molecule finished), but 4
> > molecules still did not finish.
> >
>
> Actually it looks tasks worked fine:
> bash-3.1$ cat MolDyn-244-63ar6atbg2ae1.log |grep "type=1.*ubmitted"|wc
> 24309 243090 2806214
> bash-3.1$ cat MolDyn-244-63ar6atbg2ae1.log |grep "type=1.*ailed"|wc
> 3614 36140 405816
> bash-3.1$ cat MolDyn-244-63ar6atbg2ae1.log |grep "type=1.*ompleted"|wc
> 20695 206950 2389556
>
> All tasks are accounted for. It may be that some jobs failed 3 times in a row.
> From the logs it looks like the workflow almost finished and it got to the
> point where the error reporting was to be done. Perhaps the stack overflow that
> you saw occurred there, and perhaps the impossible size of the workflow might
> have something to do with it.
>
The same machine (tg-v024) that we had trouble with before acted up again, I
should have removed it before we started the experiment. If this is the
consensus, we can certainly try it again, and make sure this machine is not in
the resource pool. Another idea is to increase the retry # from 3 to something
higher, maybe 10, 30, etc? Jobs can be resubmitted relatively fast with
Falkon, so retrying many times is not a big overhead... except that it takes
longer for Swift to give up!
Ioan
--
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
From bugzilla-daemon at mcs.anl.gov Sun Jul 1 00:47:49 2007
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sun, 1 Jul 2007 00:47:49 -0500 (CDT)
Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
In-Reply-To:
Message-ID: <20070701054749.8E478164DB@foxtrot.mcs.anl.gov>
http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=72
------- Comment #8 from iraicu at cs.uchicago.edu 2007-07-01 00:47 -------
(In reply to comment #5)
> First of all, can you commit the changes to SVN?
>
Yong made the changes, I am sure he will commit them the first chance he gets!
> (In reply to comment #4)
> > We fixed the potential synchronization issue
> > Mihael pointed out.
>
> There were two.
>
I meant to say "issues"... from the discussion I had with Yong, I believe he
addressed both of them.
> > We also fixed a badly handled exception we had in the
> > Falkon provider, that would give up very easily and exit the Falkon provider
> > thread in case of an exception, even if it wasn't a fatal one. This time
> > around, we changed the logic to simply print the exception, if there were any,
> > and not exit the Falkon provider, just continue. Personally, I think this
> > logic on handling exceptions in the Falkon provider was causing the Falkon
> > provider to exit prematurely, and hence not send any more tasks to Falkon...
>
> I can't seem to find anything that would fit that profile in the provider code.
> Can you be more specific? If the provider was setting the status of the task to
> failed, then it doesn't matter. Swift retries failed things.
>
Sure. Double check file SubmissionThread.java, notice that the thread will
live as long as exit is not set...
Line 54: public void run() {
while(!exit) {
exit is initially set to false, but anything that sets it to true, and the
submission thread will exit.
Notice the end of the file with the setStatus(Executable) function:
Line 98: public void setStatus (Executable execs[]) {
try {
for (int i=0; i > note that Swift was setting the set status of submitted tasks to the Falkon
> > provider in a separate thread,
>
> Swift does not set status of tasks. That's what the provider is supposed to do.
>
OK, there are several separate threads, one that sets the status of the task
for Swift, another that performs the submit, another that receives
notifications, etc. The common data structure between the set status thread
and the submit thread is a queue; if the submission thread dies, the queue is
still valid, and the set status thread could still insert tasks into the queue
and set the status to submitted, although there would be no submission thread
alive to perform the submission itself to Falkon.
> > which was not necesarly exiting when the Falkon
> > provider was, and hence we had the scenario in which Swift thought it sent out
> > more tasks than Falkon really saw.
>
> Can you be more specific? If there is a problem in Swift, we need to fix it,
> but your comment is too vague.
>
> >
> > Now, the issue that I think stopped this experiment. On the console of Swift,
> > the last thing that it printed was a "stack overflow error"; I don't think this
> > printed in the logs, just on the console.
>
> Without the stack trace, the information is not very useful.
>
Nika said it was simply a message printed on the console. This was the same as
the case we saw on Thursday. This was not a regular exception that Swift or
the Falkon provider controlled, and hence that it would have a print stack
trace along with it. As far as I could tell, it was an error from the JVM, and
was not accompanied by any stack trace. If you don't know where to even start
looking, let's run some quick synthetic runs of 20K jobs on Monday together,
and hopefully we can reproduce the stack overflow error, and you can see it in
person!
Ioan
> >
> > Ioan
> >
>
--
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
From hategan at mcs.anl.gov Sun Jul 1 01:53:43 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Sun, 01 Jul 2007 01:53:43 -0500
Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
In-Reply-To: <1702663950-1183255865-cardhu_decombobulator_blackberry.rim.net-1244943269-@bxe006.bisx.prod.on.blackberry>
References:
<20070630225207.B70D916506@foxtrot.mcs.anl.gov>
<1702663950-1183255865-cardhu_decombobulator_blackberry.rim.net-1244943269-@bxe006.bisx.prod.on.blackberry>
Message-ID: <1183272823.21185.5.camel@blabla.mcs.anl.gov>
On Sun, 2007-07-01 at 02:10 +0000, Ian Foster wrote:
> Why do you say the workflow's size was "impossible"? It doesn't seem that large to me. We'd like to run larger ones!
Most certainly so. However, we want to make use of loops rather than
generating large swift files.
>
>
> Sent via BlackBerry from T-Mobile
>
> -----Original Message-----
> From: bugzilla-daemon at mcs.anl.gov
>
> Date: Sat, 30 Jun 2007 17:52:07
> To:swift-devel at ci.uchicago.edu
> Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
>
>
> http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=72
>
>
>
>
>
> ------- Comment #6 from hategan at mcs.anl.gov 2007-06-30 17:52 -------
> (In reply to comment #4)
> > Hi again,
> > Here is an update of yesterday's 244 molecule run. The experiment ran further
> > than before, but it still did not complete. There were 240 molecules that
> > completed successfully (in the previous run, no molecule finished), but 4
> > molecules still did not finish.
> >
>
> Actually it looks tasks worked fine:
> bash-3.1$ cat MolDyn-244-63ar6atbg2ae1.log |grep "type=1.*ubmitted"|wc
> 24309 243090 2806214
> bash-3.1$ cat MolDyn-244-63ar6atbg2ae1.log |grep "type=1.*ailed"|wc
> 3614 36140 405816
> bash-3.1$ cat MolDyn-244-63ar6atbg2ae1.log |grep "type=1.*ompleted"|wc
> 20695 206950 2389556
>
> All tasks are accounted for. It may be that some jobs failed 3 times in a row.
> >From the logs it looks like the workflow almost finished and it got to the
> point where the error reporting was to be done. Perhaps the stack overflow that
> you saw occurred there, and perhaps the impossible size of the workflow might
> have something to do with it.
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
From bugzilla-daemon at mcs.anl.gov Sun Jul 1 01:56:28 2007
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sun, 1 Jul 2007 01:56:28 -0500 (CDT)
Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
In-Reply-To:
Message-ID: <20070701065628.0C73216506@foxtrot.mcs.anl.gov>
http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=72
------- Comment #9 from hategan at mcs.anl.gov 2007-07-01 01:56 -------
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #4)
> The same machine (tg-v024) that we had trouble with before acted up again, I
> should have removed it before we started the experiment. If this is the
> consensus, we can certainly try it again, and make sure this machine is not in
> the resource pool. Another idea is to increase the retry # from 3 to something
> higher, maybe 10, 30, etc?
Not a good idea in the general case, since many times the error may not be
something temporary. The swift scheduler takes bad machines into account and
attempts to avoid submitting to them.
>
> Ioan
>
--
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
From hategan at mcs.anl.gov Sun Jul 1 02:11:49 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Sun, 01 Jul 2007 02:11:49 -0500
Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
In-Reply-To: <1183272823.21185.5.camel@blabla.mcs.anl.gov>
References:
<20070630225207.B70D916506@foxtrot.mcs.anl.gov>
<1702663950-1183255865-cardhu_decombobulator_blackberry.rim.net-1244943269-@bxe006.bisx.prod.on.blackberry>
<1183272823.21185.5.camel@blabla.mcs.anl.gov>
Message-ID: <1183273909.21185.11.camel@blabla.mcs.anl.gov>
On Sun, 2007-07-01 at 01:53 -0500, Mihael Hategan wrote:
> On Sun, 2007-07-01 at 02:10 +0000, Ian Foster wrote:
> > Why do you say the workflow's size was "impossible"? It doesn't seem that large to me. We'd like to run larger ones!
>
> Most certainly so. However, we want to make use of loops rather than
> generating large swift files.
Ok. I see. I meant impossible size of the source file. We clearly want
to be running workflows with that many jobs smoothly. I just don't think
large source files (whether Swift or Karajan) are a good way to do it.
I'm quite (pleasantly) surprised that Swift/Karajan can load and run XML
files with 1M+ lines.
Of course, that doesn't mean we shouldn't try to fix the problems that
might arise with large source files if possible.
>
> >
> >
> > Sent via BlackBerry from T-Mobile
> >
> > -----Original Message-----
> > From: bugzilla-daemon at mcs.anl.gov
> >
> > Date: Sat, 30 Jun 2007 17:52:07
> > To:swift-devel at ci.uchicago.edu
> > Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
> >
> >
> > http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=72
> >
> >
> >
> >
> >
> > ------- Comment #6 from hategan at mcs.anl.gov 2007-06-30 17:52 -------
> > (In reply to comment #4)
> > > Hi again,
> > > Here is an update of yesterday's 244 molecule run. The experiment ran further
> > > than before, but it still did not complete. There were 240 molecules that
> > > completed successfully (in the previous run, no molecule finished), but 4
> > > molecules still did not finish.
> > >
> >
> > Actually it looks tasks worked fine:
> > bash-3.1$ cat MolDyn-244-63ar6atbg2ae1.log |grep "type=1.*ubmitted"|wc
> > 24309 243090 2806214
> > bash-3.1$ cat MolDyn-244-63ar6atbg2ae1.log |grep "type=1.*ailed"|wc
> > 3614 36140 405816
> > bash-3.1$ cat MolDyn-244-63ar6atbg2ae1.log |grep "type=1.*ompleted"|wc
> > 20695 206950 2389556
> >
> > All tasks are accounted for. It may be that some jobs failed 3 times in a row.
> > >From the logs it looks like the workflow almost finished and it got to the
> > point where the error reporting was to be done. Perhaps the stack overflow that
> > you saw occurred there, and perhaps the impossible size of the workflow might
> > have something to do with it.
> >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From bugzilla-daemon at mcs.anl.gov Sun Jul 1 02:15:35 2007
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sun, 1 Jul 2007 02:15:35 -0500 (CDT)
Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
In-Reply-To:
Message-ID: <20070701071535.1AE3416506@foxtrot.mcs.anl.gov>
http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=72
------- Comment #10 from hategan at mcs.anl.gov 2007-07-01 02:15 -------
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #4)
> >
> > There were two.
> >
> I meant to say "issues"... from the discussion I had with Yong, I believe he
> addressed both of them.
Ok. Got confused.
> > > We also fixed a badly handled exception we had [...]
> > Can you be more specific? [...]
> >
> Sure. Double check file SubmissionThread.java, notice that the thread will
> live as long as exit is not set...
> Also, check the StatusThread.java,
Right. Missed that.
>
> > > note that Swift was setting the set status of submitted tasks to the Falkon
> > > provider in a separate thread,
> >
> > Swift does not set status of tasks. That's what the provider is supposed to do.
> >
> OK, there are several separate threads, one that sets the status of the task
> for Swift, another that performs the submit, another that receives
> notifications, etc. The common data structure between the set status thread
> and the submit thread is a queue; if the submission thread dies, the queue is
> still valid, and the set status thread could still insert tasks into the queue
> and set the status to submitted, although there would be no submission thread
> alive to perform the submission itself to Falkon.
That sounds like the provider, not Swift. Maybe I misunderstood something?
--
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
From bugzilla-daemon at mcs.anl.gov Sun Jul 1 02:18:46 2007
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sun, 1 Jul 2007 02:18:46 -0500 (CDT)
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To:
Message-ID: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=76
------- Comment #1 from hategan at mcs.anl.gov 2007-07-01 02:18 -------
This would require a data file pointer store (VDC like thing) which can record
where intermediate files are instead of assuming they are always available on
the submit host.
--
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
From bugzilla-daemon at mcs.anl.gov Sun Jul 1 10:48:09 2007
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sun, 1 Jul 2007 10:48:09 -0500 (CDT)
Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
In-Reply-To:
Message-ID: <20070701154809.1AFB5164DB@foxtrot.mcs.anl.gov>
http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=72
------- Comment #11 from iraicu at cs.uchicago.edu 2007-07-01 10:48 -------
(In reply to comment #9)
> (In reply to comment #7)
> > (In reply to comment #6)
> > > (In reply to comment #4)
> > The same machine (tg-v024) that we had trouble with before acted up again, I
> > should have removed it before we started the experiment. If this is the
> > consensus, we can certainly try it again, and make sure this machine is not in
> > the resource pool. Another idea is to increase the retry # from 3 to something
> > higher, maybe 10, 30, etc?
>
> Not a good idea in the general case, since many times the error may not be
> something temporary. The swift scheduler takes bad machines into account and
> attempts to avoid submitting to them.
>
Yes, but in this case, Falkon was the only set of resources that were available
to Swift, so giving up early means giving up on the entire workflow. If it was
indeed that the # of failures reached up to the maximum of 3 and that is why
the worklow didn't complete, I would argue that it would be worthwhile to
increase this upper ceiling.... at least when running solely with Falkon, or at
the very least, for this experiment to see th 244 mol run succeed. Remember
that Falkon is much faster than GRAM/PBS, so if errors happen quick, as in the
case on this tg-v024 node, where it happens in <50 ms, then 1000s of errors can
happen in a matter of seconds to minutes.... I am not sure what the correct
solution is, bu something to consider as the dynamics of the problem is now
different than it was before prior to Falkon.
Ioan
> >
> > Ioan
> >
>
--
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
From bugzilla-daemon at mcs.anl.gov Sun Jul 1 10:49:46 2007
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sun, 1 Jul 2007 10:49:46 -0500 (CDT)
Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
In-Reply-To:
Message-ID: <20070701154946.60D4C164DB@foxtrot.mcs.anl.gov>
http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=72
------- Comment #12 from iraicu at cs.uchicago.edu 2007-07-01 10:49 -------
(In reply to comment #10)
> (In reply to comment #7)
> > (In reply to comment #6)
> > > (In reply to comment #4)
> > >
> > > There were two.
> > >
> > I meant to say "issues"... from the discussion I had with Yong, I believe he
> > addressed both of them.
>
> Ok. Got confused.
>
> > > > We also fixed a badly handled exception we had [...]
> > > Can you be more specific? [...]
> > >
> > Sure. Double check file SubmissionThread.java, notice that the thread will
> > live as long as exit is not set...
> > Also, check the StatusThread.java,
>
> Right. Missed that.
>
> >
> > > > note that Swift was setting the set status of submitted tasks to the Falkon
> > > > provider in a separate thread,
> > >
> > > Swift does not set status of tasks. That's what the provider is supposed to do.
> > >
> > OK, there are several separate threads, one that sets the status of the task
> > for Swift, another that performs the submit, another that receives
> > notifications, etc. The common data structure between the set status thread
> > and the submit thread is a queue; if the submission thread dies, the queue is
> > still valid, and the set status thread could still insert tasks into the queue
> > and set the status to submitted, although there would be no submission thread
> > alive to perform the submission itself to Falkon.
>
> That sounds like the provider, not Swift. Maybe I misunderstood something?
>
Right, the provider has multiple threads, and if any one of them exit
prematurely, then it cannot function correctly.
Ioan
--
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
From bugzilla-daemon at mcs.anl.gov Sun Jul 1 11:36:30 2007
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sun, 1 Jul 2007 11:36:30 -0500 (CDT)
Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
In-Reply-To:
Message-ID: <20070701163630.E977916506@foxtrot.mcs.anl.gov>
http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=72
------- Comment #13 from hategan at mcs.anl.gov 2007-07-01 11:36 -------
(In reply to comment #11)
> (In reply to comment #9)
> > (In reply to comment #7)
> > > (In reply to comment #6)
> > > > (In reply to comment #4)
> > > The same machine (tg-v024) that we had trouble with before acted up again, I
> > > should have removed it before we started the experiment. If this is the
> > > consensus, we can certainly try it again, and make sure this machine is not in
> > > the resource pool. Another idea is to increase the retry # from 3 to something
> > > higher, maybe 10, 30, etc?
> >
> > Not a good idea in the general case, since many times the error may not be
> > something temporary. The swift scheduler takes bad machines into account and
> > attempts to avoid submitting to them.
> >
> Yes, but in this case, Falkon was the only set of resources that were available
> to Swift, so giving up early means giving up on the entire workflow. If it was
> indeed that the # of failures reached up to the maximum of 3 and that is why
> the worklow didn't complete, I would argue that it would be worthwhile to
> increase this upper ceiling.... at least when running solely with Falkon, or at
> the very least, for this experiment to see th 244 mol run succeed. Remember
> that Falkon is much faster than GRAM/PBS, so if errors happen quick, as in the
> case on this tg-v024 node, where it happens in <50 ms, then 1000s of errors can
> happen in a matter of seconds to minutes.... I am not sure what the correct
> solution is, bu something to consider as the dynamics of the problem is now
> different than it was before prior to Falkon.
By themselves retries don't solve the problem. There must be a reasonable
chance that a job will finish. If you have 999 busy workers and 1 bad worker,
restarting 100 times will still cause the workflow to fail, and the fact that
restarts will happen fast is not exactly helping.
While a bit reluctant to add more options, I guess the number of restarts could
be one in the future.
>
> Ioan
> > >
> > > Ioan
> > >
> >
>
--
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
From bugzilla-daemon at mcs.anl.gov Mon Jul 2 07:58:28 2007
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Mon, 2 Jul 2007 07:58:28 -0500 (CDT)
Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
In-Reply-To:
Message-ID: <20070702125828.05B7B16506@foxtrot.mcs.anl.gov>
http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=72
------- Comment #14 from nefedova at mcs.anl.gov 2007-07-02 07:58 -------
This is what I had on stdout (stack overflow error). The last line was printed
over and over again 100s of times.
*****************************SUPER_DEBUG: waiting for notification...
chrm_long completed
Exception in thread "Worker 3" java.lang.StackOverflowError
at java.util.ArrayList.addAll(ArrayList.java:472)
at
org.globus.cog.karajan.arguments.VariableArgumentsImpl.appendAll(VariableArgumentsImpl.java:79)
at
org.globus.cog.karajan.workflow.futures.FutureVariableArguments.appendAll(FutureVariableArguments.java:40)
at
org.globus.cog.karajan.arguments.OrderedParallelVariableArguments.flushBuffer(OrderedParallelVariableArguments.java:67)
at
org.globus.cog.karajan.arguments.OrderedParallelVariableArguments.prevClosed(OrderedParallelVariableArguments.java:73)
at
org.globus.cog.karajan.arguments.OrderedParallelVariableArguments.prevClosed(OrderedParallelVariableArguments.java:78)
at
org.globus.cog.karajan.arguments.OrderedParallelVariableArguments.prevClosed(OrderedParallelVariableArguments.java:78)
--
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
From bugzilla-daemon at mcs.anl.gov Mon Jul 2 09:17:11 2007
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Mon, 2 Jul 2007 09:17:11 -0500 (CDT)
Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
In-Reply-To:
Message-ID: <20070702141711.DC3B516506@foxtrot.mcs.anl.gov>
http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=72
------- Comment #15 from hategan at mcs.anl.gov 2007-07-02 09:17 -------
(In reply to comment #14)
> Exception in thread "Worker 3" java.lang.StackOverflowError
> [...]
> org.globus.cog.karajan.arguments.OrderedParallelVariableArguments.prevClosed(OrderedParallelVariableArguments.java:78)
> at
> org.globus.cog.karajan.arguments.OrderedParallelVariableArguments.prevClosed(OrderedParallelVariableArguments.java:78)
>
> (repeat ad nauseaum)
Fix to Karajan committed. Needs testing since it's in a delicate place.
--
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
From benc at hawaga.org.uk Mon Jul 2 13:42:30 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Tue, 3 Jul 2007 00:12:30 +0530 (IST)
Subject: [Swift-devel] @strcut
Message-ID:
r881 makes a quick-and-dirty regexp function, @strcut, available. It
doesn't handle errors nicely (or at all), but I've put it in so Nika can
experiment with it a bit in an attempt to reduce her SwiftScript code
size.
If its useful, I'll tidy it up, otherwise I'll back it out.
--
From foster at mcs.anl.gov Mon Jul 2 14:05:54 2007
From: foster at mcs.anl.gov (Ian Foster)
Date: Mon, 02 Jul 2007 14:05:54 -0500
Subject: [Swift-devel] @strcut
In-Reply-To:
References:
Message-ID: <46894C92.6090602@mcs.anl.gov>
Hi,
I am curious--is this the only reason why the MolDyn program is so
large, or are there other things that can be done to reduce code size?
Ian.
Ben Clifford wrote:
> r881 makes a quick-and-dirty regexp function, @strcut, available. It
> doesn't handle errors nicely (or at all), but I've put it in so Nika can
> experiment with it a bit in an attempt to reduce her SwiftScript code
> size.
>
> If its useful, I'll tidy it up, otherwise I'll back it out.
>
>
--
Ian Foster, Director, Computation Institute
Argonne National Laboratory & University of Chicago
Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439
Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637
Tel: +1 630 252 4619. Web: www.ci.uchicago.edu.
Globus Alliance: www.globus.org.
From nefedova at mcs.anl.gov Mon Jul 2 14:16:44 2007
From: nefedova at mcs.anl.gov (Veronika Nefedova)
Date: Mon, 2 Jul 2007 14:16:44 -0500
Subject: [Swift-devel] @strcut
In-Reply-To: <46894C92.6090602@mcs.anl.gov>
References:
<46894C92.6090602@mcs.anl.gov>
Message-ID: <33F67BC7-F2CD-4402-89F9-C27AF8162A6F@mcs.anl.gov>
this is the main thing that prevented me from using loops. Once I re-
write it with loops, the size of the code would be reduced dramatically.
On Jul 2, 2007, at 2:05 PM, Ian Foster wrote:
> Hi,
>
> I am curious--is this the only reason why the MolDyn program is so
> large, or are there other things that can be done to reduce code size?
>
> Ian.
>
> Ben Clifford wrote:
>> r881 makes a quick-and-dirty regexp function, @strcut, available.
>> It doesn't handle errors nicely (or at all), but I've put it in so
>> Nika can experiment with it a bit in an attempt to reduce her
>> SwiftScript code size.
>>
>> If its useful, I'll tidy it up, otherwise I'll back it out.
>>
>>
>
> --
>
> Ian Foster, Director, Computation Institute
> Argonne National Laboratory & University of Chicago
> Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439
> Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637
> Tel: +1 630 252 4619. Web: www.ci.uchicago.edu.
> Globus Alliance: www.globus.org.
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From foster at mcs.anl.gov Mon Jul 2 14:17:11 2007
From: foster at mcs.anl.gov (Ian Foster)
Date: Mon, 02 Jul 2007 14:17:11 -0500
Subject: [Swift-devel] @strcut
In-Reply-To: <33F67BC7-F2CD-4402-89F9-C27AF8162A6F@mcs.anl.gov>
References:
<46894C92.6090602@mcs.anl.gov>
<33F67BC7-F2CD-4402-89F9-C27AF8162A6F@mcs.anl.gov>
Message-ID: <46894F37.5000506@mcs.anl.gov>
cool ...
Veronika Nefedova wrote:
> this is the main thing that prevented me from using loops. Once I
> re-write it with loops, the size of the code would be reduced
> dramatically.
>
> On Jul 2, 2007, at 2:05 PM, Ian Foster wrote:
>
>> Hi,
>>
>> I am curious--is this the only reason why the MolDyn program is so
>> large, or are there other things that can be done to reduce code size?
>>
>> Ian.
>>
>> Ben Clifford wrote:
>>> r881 makes a quick-and-dirty regexp function, @strcut, available. It
>>> doesn't handle errors nicely (or at all), but I've put it in so Nika
>>> can experiment with it a bit in an attempt to reduce her SwiftScript
>>> code size.
>>>
>>> If its useful, I'll tidy it up, otherwise I'll back it out.
>>>
>>>
>>
>> --
>>
>> Ian Foster, Director, Computation Institute
>> Argonne National Laboratory & University of Chicago
>> Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439
>> Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637
>> Tel: +1 630 252 4619. Web: www.ci.uchicago.edu.
>> Globus Alliance: www.globus.org.
>>
>> _______________________________________________
>> Swift-devel mailing list
>> Swift-devel at ci.uchicago.edu
>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>
>
--
Ian Foster, Director, Computation Institute
Argonne National Laboratory & University of Chicago
Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439
Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637
Tel: +1 630 252 4619. Web: www.ci.uchicago.edu.
Globus Alliance: www.globus.org.
From hategan at mcs.anl.gov Mon Jul 2 14:47:26 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Mon, 02 Jul 2007 14:47:26 -0500
Subject: [Swift-devel] @strcut
In-Reply-To:
References:
Message-ID: <1183405646.21420.1.camel@blabla.mcs.anl.gov>
Something like that should be added to the Karajan system library too.
On Tue, 2007-07-03 at 00:12 +0530, Ben Clifford wrote:
> r881 makes a quick-and-dirty regexp function, @strcut, available. It
> doesn't handle errors nicely (or at all), but I've put it in so Nika can
> experiment with it a bit in an attempt to reduce her SwiftScript code
> size.
>
> If its useful, I'll tidy it up, otherwise I'll back it out.
>
From benc at hawaga.org.uk Mon Jul 2 20:08:56 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Tue, 3 Jul 2007 06:38:56 +0530 (IST)
Subject: [Swift-devel] recent karajan changes causing trouble
Message-ID:
I get the below when I try to run a hello world workflow
(examples/tutorial/q1.swift).
I think Nika also saw something that looks similar, with a different
workflow.
This is with cog r1655.
I reverted my checkout to cog r1650 (svn merge -r1655:1650 .) and hello
world runs ok (r1650 being before the most recent set of cog commits).
$ swift -debug q1.swift
Recompilation suppressed.
null
kernel:cache @ sys.xml, line: 3
Caused by: java.lang.UnsupportedOperationException
at java.util.AbstractMap.put(AbstractMap.java:228)
at
org.globus.cog.karajan.workflow.nodes.CacheNode.getTrackingArguments(CacheNode.java:153)
at
org.globus.cog.karajan.workflow.nodes.CacheNode.post(CacheNode.java:77)
at
org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArguments.childCompleted(AbstractSequentialWithArguments.java:192)
at
org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.nonArgChildCompleted(PartialArgumentsContainer.java:90)
at
org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.childCompleted(PartialArgumentsContainer.java:85)
at
org.globus.cog.karajan.workflow.nodes.Sequential.notificationEvent(Sequential.java:33)
at
org.globus.cog.karajan.workflow.nodes.CacheNode.notificationEvent(CacheNode.java:111)
at
org.globus.cog.karajan.workflow.nodes.FlowNode.event(FlowNode.java:334)
at
org.globus.cog.karajan.workflow.events.EventBus.send(EventBus.java:123)
at
org.globus.cog.karajan.workflow.events.EventBus.sendHooked(EventBus.java:97)
at
org.globus.cog.karajan.workflow.nodes.FlowNode.fireNotificationEvent(FlowNode.java:172)
at
org.globus.cog.karajan.workflow.nodes.FlowNode.complete(FlowNode.java:298)
at
org.globus.cog.karajan.workflow.nodes.FlowContainer.post(FlowContainer.java:58)
at
org.globus.cog.karajan.workflow.nodes.Namespace.post(Namespace.java:40)
at
org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArguments.childCompleted(AbstractSequentialWithArguments.java:192)
at
org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.nonArgChildCompleted(PartialArgumentsContainer.java:90)
--
From hategan at mcs.anl.gov Mon Jul 2 21:23:37 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Mon, 02 Jul 2007 21:23:37 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
Message-ID: <1183429417.16404.0.camel@blabla.mcs.anl.gov>
Yup. Try now.
On Tue, 2007-07-03 at 06:38 +0530, Ben Clifford wrote:
> I get the below when I try to run a hello world workflow
> (examples/tutorial/q1.swift).
>
> I think Nika also saw something that looks similar, with a different
> workflow.
>
> This is with cog r1655.
>
> I reverted my checkout to cog r1650 (svn merge -r1655:1650 .) and hello
> world runs ok (r1650 being before the most recent set of cog commits).
>
>
> $ swift -debug q1.swift
> Recompilation suppressed.
>
> null
> kernel:cache @ sys.xml, line: 3
> Caused by: java.lang.UnsupportedOperationException
> at java.util.AbstractMap.put(AbstractMap.java:228)
> at
> org.globus.cog.karajan.workflow.nodes.CacheNode.getTrackingArguments(CacheNode.java:153)
> at
> org.globus.cog.karajan.workflow.nodes.CacheNode.post(CacheNode.java:77)
> at
> org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArguments.childCompleted(AbstractSequentialWithArguments.java:192)
> at
> org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.nonArgChildCompleted(PartialArgumentsContainer.java:90)
> at
> org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.childCompleted(PartialArgumentsContainer.java:85)
> at
> org.globus.cog.karajan.workflow.nodes.Sequential.notificationEvent(Sequential.java:33)
> at
> org.globus.cog.karajan.workflow.nodes.CacheNode.notificationEvent(CacheNode.java:111)
> at
> org.globus.cog.karajan.workflow.nodes.FlowNode.event(FlowNode.java:334)
> at
> org.globus.cog.karajan.workflow.events.EventBus.send(EventBus.java:123)
> at
> org.globus.cog.karajan.workflow.events.EventBus.sendHooked(EventBus.java:97)
> at
> org.globus.cog.karajan.workflow.nodes.FlowNode.fireNotificationEvent(FlowNode.java:172)
> at
> org.globus.cog.karajan.workflow.nodes.FlowNode.complete(FlowNode.java:298)
> at
> org.globus.cog.karajan.workflow.nodes.FlowContainer.post(FlowContainer.java:58)
> at
> org.globus.cog.karajan.workflow.nodes.Namespace.post(Namespace.java:40)
> at
> org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArguments.childCompleted(AbstractSequentialWithArguments.java:192)
> at
> org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.nonArgChildCompleted(PartialArgumentsContainer.java:90)
>
>
From benc at hawaga.org.uk Mon Jul 2 22:40:11 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Tue, 3 Jul 2007 03:40:11 +0000 (GMT)
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To: <1183429417.16404.0.camel@blabla.mcs.anl.gov>
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
Message-ID:
On Mon, 2 Jul 2007, Mihael Hategan wrote:
> Yup. Try now.
>
works
--
From benc at hawaga.org.uk Tue Jul 3 12:53:30 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Tue, 3 Jul 2007 23:23:30 +0530 (IST)
Subject: [Swift-devel] mapper syntax
Message-ID:
The syntax:
imagefiles if[]
;
is rather noisy all on one line.
A syntax change could be to express the above as:
imagefiles if[] map my_mapper {
foo = @strcat(filename,blah);
otherparam = true;
moreparams = false;
};
--
From benc at hawaga.org.uk Tue Jul 3 12:50:35 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Tue, 3 Jul 2007 23:20:35 +0530 (IST)
Subject: [Swift-devel] xml tc.data format
Message-ID:
I'd like to make tc.data be formatted as XML:
i) the present tab-deliminated format has usability issues (pretty much
the same as Makefile has). tabs are used for a reason (I think because
some fields in the file can have spaces in them, or something like that).
ii) it would be more consistent with the sites.xml format.
--
From hategan at mcs.anl.gov Tue Jul 3 13:01:47 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Tue, 03 Jul 2007 13:01:47 -0500
Subject: [Swift-devel] mapper syntax
In-Reply-To:
References:
Message-ID: <1183485707.17547.2.camel@blabla.mcs.anl.gov>
On Tue, 2007-07-03 at 23:23 +0530, Ben Clifford wrote:
> The syntax:
>
> imagefiles if[]
> ;
>
> is rather noisy all on one line.
>
> A syntax change could be to express the above as:
>
> imagefiles if[] map my_mapper {
What if "map" be replaced by some operator (":", "~", "#")?
> foo = @strcat(filename,blah);
> otherparam = true;
> moreparams = false;
> };
The semicolon should not be required after a '}'.
>
>
From hategan at mcs.anl.gov Tue Jul 3 13:04:09 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Tue, 03 Jul 2007 13:04:09 -0500
Subject: [Swift-devel] xml tc.data format
In-Reply-To:
References:
Message-ID: <1183485849.17547.5.camel@blabla.mcs.anl.gov>
On Tue, 2007-07-03 at 23:20 +0530, Ben Clifford wrote:
> I'd like to make tc.data be formatted as XML:
>
> i) the present tab-deliminated format has usability issues (pretty much
> the same as Makefile has). tabs are used for a reason (I think because
> some fields in the file can have spaces in them, or something like that).
1. Having named args (attributes) would make it easier to skip some of
them instead of writing NULL (or was it null?).
2. The code for parsing it would be much simpler, and we could probably
remove the dependency on vds.
>
> ii) it would be more consistent with the sites.xml format.
>
From benc at hawaga.org.uk Tue Jul 3 14:33:51 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Tue, 3 Jul 2007 19:33:51 +0000 (GMT)
Subject: [Swift-devel] xml tc.data format
In-Reply-To: <1183485849.17547.5.camel@blabla.mcs.anl.gov>
References:
<1183485849.17547.5.camel@blabla.mcs.anl.gov>
Message-ID:
another thing i was thinking about for the config file formats, is to
change profile specification from:
5
which is how profiles are represented in the VDS1-style sites.xml
to a more document-like(?) form such as:
5
This makes better use of XML structure, but I don't know how it would fit
(perhaps quite badly) into the present way in which the swift code reads
in sites.xml.
--
From hategan at mcs.anl.gov Tue Jul 3 14:37:20 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Tue, 03 Jul 2007 14:37:20 -0500
Subject: [Swift-devel] xml tc.data format
In-Reply-To:
References:
<1183485849.17547.5.camel@blabla.mcs.anl.gov>
Message-ID: <1183491440.24728.1.camel@blabla.mcs.anl.gov>
On Tue, 2007-07-03 at 19:33 +0000, Ben Clifford wrote:
> another thing i was thinking about for the config file formats, is to
> change profile specification from:
>
> 5
>
> which is how profiles are represented in the VDS1-style sites.xml
>
> to a more document-like(?) form such as:
>
> 5
>
> This makes better use of XML structure, but I don't know how it would fit
> (perhaps quite badly) into the present way in which the swift code reads
> in sites.xml.
You'd have to pre-define things, so you won't get the flexibility of
dynamic properties.
>
From benc at hawaga.org.uk Tue Jul 3 23:34:25 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Wed, 4 Jul 2007 10:04:25 +0530 (IST)
Subject: [Swift-devel] xml tc.data format
In-Reply-To: <1183485849.17547.5.camel@blabla.mcs.anl.gov>
References:
<1183485849.17547.5.camel@blabla.mcs.anl.gov>
Message-ID:
On Tue, 3 Jul 2007, Mihael Hategan wrote:
> 2. The code for parsing it would be much simpler, and we could probably
> remove the dependency on vds.
VDSScheduler uses the RoundRobin site selector from VDS1.
But people aren't using VDSScheduler so that can probably go away too.
--
From benc at hawaga.org.uk Wed Jul 4 02:02:23 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Wed, 4 Jul 2007 12:32:23 +0530 (IST)
Subject: [Swift-devel] license
Message-ID:
There's a jar file in lib/ called: jug-lgpl-2.0.0.jar
The filename might suggest that this is subject to the LGPL.
Does anyone know?
--
From benc at hawaga.org.uk Wed Jul 4 00:37:39 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Wed, 4 Jul 2007 11:07:39 +0530 (IST)
Subject: [Swift-devel] dot files by default
Message-ID:
does anyone have preference about whether .dot graphviz files are
generated by default or not?
I find them a bit annoying in as much as they double the number of run
files in my working directories to no immediate benefit.
--
From hategan at mcs.anl.gov Wed Jul 4 22:57:28 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Wed, 04 Jul 2007 22:57:28 -0500
Subject: [Swift-devel] license
In-Reply-To:
References:
Message-ID: <1183607848.3638.1.camel@blabla.mcs.anl.gov>
Yes. It's actually available in 2 licenses.
http://jug.safehaus.org/Download
On Wed, 2007-07-04 at 12:32 +0530, Ben Clifford wrote:
> There's a jar file in lib/ called: jug-lgpl-2.0.0.jar
>
> The filename might suggest that this is subject to the LGPL.
>
> Does anyone know?
>
From benc at hawaga.org.uk Wed Jul 4 23:02:14 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 04:02:14 +0000 (GMT)
Subject: [Swift-devel] license
In-Reply-To: <1183607848.3638.1.camel@blabla.mcs.anl.gov>
References:
<1183607848.3638.1.camel@blabla.mcs.anl.gov>
Message-ID:
ok cool. I suspect the dev.globus incubatorgods will be happier with the
ASL one. Funny that they have separate jar files for each license.
On Wed, 4 Jul 2007, Mihael Hategan wrote:
> Yes. It's actually available in 2 licenses.
> http://jug.safehaus.org/Download
>
> On Wed, 2007-07-04 at 12:32 +0530, Ben Clifford wrote:
> > There's a jar file in lib/ called: jug-lgpl-2.0.0.jar
> >
> > The filename might suggest that this is subject to the LGPL.
> >
> > Does anyone know?
> >
>
>
From hategan at mcs.anl.gov Wed Jul 4 23:09:46 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Wed, 04 Jul 2007 23:09:46 -0500
Subject: [Swift-devel] license
In-Reply-To:
References:
<1183607848.3638.1.camel@blabla.mcs.anl.gov>
Message-ID: <1183608586.4172.0.camel@blabla.mcs.anl.gov>
What's wrong with LGPL now?
On Thu, 2007-07-05 at 04:02 +0000, Ben Clifford wrote:
> ok cool. I suspect the dev.globus incubatorgods will be happier with the
> ASL one. Funny that they have separate jar files for each license.
>
> On Wed, 4 Jul 2007, Mihael Hategan wrote:
>
> > Yes. It's actually available in 2 licenses.
> > http://jug.safehaus.org/Download
> >
> > On Wed, 2007-07-04 at 12:32 +0530, Ben Clifford wrote:
> > > There's a jar file in lib/ called: jug-lgpl-2.0.0.jar
> > >
> > > The filename might suggest that this is subject to the LGPL.
> > >
> > > Does anyone know?
> > >
> >
> >
>
From benc at hawaga.org.uk Wed Jul 4 23:13:29 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 04:13:29 +0000 (GMT)
Subject: [Swift-devel] license
In-Reply-To: <1183608586.4172.0.camel@blabla.mcs.anl.gov>
References:
<1183607848.3638.1.camel@blabla.mcs.anl.gov>
<1183608586.4172.0.camel@blabla.mcs.anl.gov>
Message-ID:
paranoid lawyers?
On Wed, 4 Jul 2007, Mihael Hategan wrote:
> What's wrong with LGPL now?
>
> On Thu, 2007-07-05 at 04:02 +0000, Ben Clifford wrote:
> > ok cool. I suspect the dev.globus incubatorgods will be happier with the
> > ASL one. Funny that they have separate jar files for each license.
> >
> > On Wed, 4 Jul 2007, Mihael Hategan wrote:
> >
> > > Yes. It's actually available in 2 licenses.
> > > http://jug.safehaus.org/Download
> > >
> > > On Wed, 2007-07-04 at 12:32 +0530, Ben Clifford wrote:
> > > > There's a jar file in lib/ called: jug-lgpl-2.0.0.jar
> > > >
> > > > The filename might suggest that this is subject to the LGPL.
> > > >
> > > > Does anyone know?
> > > >
> > >
> > >
> >
>
>
From benc at hawaga.org.uk Wed Jul 4 23:41:38 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 04:41:38 +0000 (GMT)
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
Message-ID:
I don't think that's true.
If data files are labelled with URIs rather than
paths-relative-to-submit-directory, then those URIs are understandable
without a VDC-as-entity.
You don't need a separate VDC to tell you how to get at myfile here:
file myfile <"gsiftp://terminable.ci.uchicago.edu/scratch/foo/">;
The 'data file pointer store' exists already - its the hierarchical
namespace that is rooted in IANA's management of the URI and DNS space,
continues to UC's management of DNS space and then down to my management
of terminable's filesystem space and then down to whoever owns the foo
directory.
On Sun, 1 Jul 2007, bugzilla-daemon at mcs.anl.gov wrote:
> http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=76
>
>
>
>
>
> ------- Comment #1 from hategan at mcs.anl.gov 2007-07-01 02:18 -------
> This would require a data file pointer store (VDC like thing) which can record
> where intermediate files are instead of assuming they are always available on
> the submit host.
>
>
>
From benc at hawaga.org.uk Thu Jul 5 01:18:10 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 11:48:10 +0530 (IST)
Subject: [Swift-devel] language behaviour tests
Message-ID:
In r891 I put in some language behaviour tests in
tests/language-behaviour/
These run a bunch of small SwiftScript programs locally and check that
they output expected text - for example, checking that @strcat really does
concatenate, that + really does add, and other such things.
I built them for testing various changes I've been playing with at the
language parsing and compilation layer.
Previously I was using the tests
in tests/language/ for testing parser changes.
The language/ tests check that input SwiftScript always produces the same
.xml intermediate form, whilst these new tests check that the input
SwiftScript always produces the same output (in a file) on execution,
without regard to whether the .xml and .kml intermediate files take a
different form or not.
--
From nefedova at mcs.anl.gov Thu Jul 5 08:34:39 2007
From: nefedova at mcs.anl.gov (Veronika Nefedova)
Date: Thu, 5 Jul 2007 08:34:39 -0500
Subject: [Swift-devel] dot files by default
In-Reply-To:
References:
Message-ID: <69D182A1-2658-4B6E-85E7-6B86ECB97A13@mcs.anl.gov>
It would've been even better if these dot files were generated
correctly. There is Bug #35 about it...
Nika
On Jul 4, 2007, at 12:37 AM, Ben Clifford wrote:
> does anyone have preference about whether .dot graphviz files are
> generated by default or not?
>
> I find them a bit annoying in as much as they double the number of run
> files in my working directories to no immediate benefit.
>
> --
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From hategan at mcs.anl.gov Thu Jul 5 08:55:31 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Thu, 05 Jul 2007 08:55:31 -0500
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To:
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
Message-ID: <1183643731.5084.3.camel@blabla.mcs.anl.gov>
I think you're missing something. You need to remember where the files
are. The mapping information becomes insufficient. It tells you where
some initial files were, but it won't contain any site information. And
that's good, because the decision of where something is done is made at
run-time. But you still need some store (even though probably
memory-based and only persistent through one swift run).
On Thu, 2007-07-05 at 04:41 +0000, Ben Clifford wrote:
> I don't think that's true.
>
> If data files are labelled with URIs rather than
> paths-relative-to-submit-directory, then those URIs are understandable
> without a VDC-as-entity.
>
> You don't need a separate VDC to tell you how to get at myfile here:
>
> file myfile <"gsiftp://terminable.ci.uchicago.edu/scratch/foo/">;
>
> The 'data file pointer store' exists already - its the hierarchical
> namespace that is rooted in IANA's management of the URI and DNS space,
> continues to UC's management of DNS space and then down to my management
> of terminable's filesystem space and then down to whoever owns the foo
> directory.
>
>
> On Sun, 1 Jul 2007, bugzilla-daemon at mcs.anl.gov wrote:
>
> > http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=76
> >
> >
> >
> >
> >
> > ------- Comment #1 from hategan at mcs.anl.gov 2007-07-01 02:18 -------
> > This would require a data file pointer store (VDC like thing) which can record
> > where intermediate files are instead of assuming they are always available on
> > the submit host.
> >
> >
> >
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From hategan at mcs.anl.gov Thu Jul 5 08:59:16 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Thu, 05 Jul 2007 08:59:16 -0500
Subject: [Swift-devel] dot files by default
In-Reply-To: <69D182A1-2658-4B6E-85E7-6B86ECB97A13@mcs.anl.gov>
References:
<69D182A1-2658-4B6E-85E7-6B86ECB97A13@mcs.anl.gov>
Message-ID: <1183643956.5084.7.camel@blabla.mcs.anl.gov>
On Thu, 2007-07-05 at 08:34 -0500, Veronika Nefedova wrote:
> It would've been even better if these dot files were generated
> correctly. There is Bug #35 about it...
That's helpful ;)
>
> Nika
>
> On Jul 4, 2007, at 12:37 AM, Ben Clifford wrote:
>
> > does anyone have preference about whether .dot graphviz files are
> > generated by default or not?
> >
> > I find them a bit annoying in as much as they double the number of run
> > files in my working directories to no immediate benefit.
> >
> > --
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From benc at hawaga.org.uk Thu Jul 5 09:05:17 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 14:05:17 +0000 (GMT)
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To: <1183643731.5084.3.camel@blabla.mcs.anl.gov>
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
<1183643731.5084.3.camel@blabla.mcs.anl.gov>
Message-ID:
how does it know where files are now, between jobs?
On Thu, 5 Jul 2007, Mihael Hategan wrote:
> I think you're missing something. You need to remember where the files
> are. The mapping information becomes insufficient. It tells you where
> some initial files were, but it won't contain any site information. And
> that's good, because the decision of where something is done is made at
> run-time. But you still need some store (even though probably
> memory-based and only persistent through one swift run).
>
> On Thu, 2007-07-05 at 04:41 +0000, Ben Clifford wrote:
> > I don't think that's true.
> >
> > If data files are labelled with URIs rather than
> > paths-relative-to-submit-directory, then those URIs are understandable
> > without a VDC-as-entity.
> >
> > You don't need a separate VDC to tell you how to get at myfile here:
> >
> > file myfile <"gsiftp://terminable.ci.uchicago.edu/scratch/foo/">;
> >
> > The 'data file pointer store' exists already - its the hierarchical
> > namespace that is rooted in IANA's management of the URI and DNS space,
> > continues to UC's management of DNS space and then down to my management
> > of terminable's filesystem space and then down to whoever owns the foo
> > directory.
> >
> >
> > On Sun, 1 Jul 2007, bugzilla-daemon at mcs.anl.gov wrote:
> >
> > > http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=76
> > >
> > >
> > >
> > >
> > >
> > > ------- Comment #1 from hategan at mcs.anl.gov 2007-07-01 02:18 -------
> > > This would require a data file pointer store (VDC like thing) which can record
> > > where intermediate files are instead of assuming they are always available on
> > > the submit host.
> > >
> > >
> > >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
>
>
From hategan at mcs.anl.gov Thu Jul 5 09:10:07 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Thu, 05 Jul 2007 09:10:07 -0500
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To:
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
<1183643731.5084.3.camel@blabla.mcs.anl.gov>
Message-ID: <1183644607.5084.9.camel@blabla.mcs.anl.gov>
On Thu, 2007-07-05 at 14:05 +0000, Ben Clifford wrote:
> how does it know where files are now, between jobs?
That's the thing. They're always on localhost.
>
> On Thu, 5 Jul 2007, Mihael Hategan wrote:
>
> > I think you're missing something. You need to remember where the files
> > are. The mapping information becomes insufficient. It tells you where
> > some initial files were, but it won't contain any site information. And
> > that's good, because the decision of where something is done is made at
> > run-time. But you still need some store (even though probably
> > memory-based and only persistent through one swift run).
> >
> > On Thu, 2007-07-05 at 04:41 +0000, Ben Clifford wrote:
> > > I don't think that's true.
> > >
> > > If data files are labelled with URIs rather than
> > > paths-relative-to-submit-directory, then those URIs are understandable
> > > without a VDC-as-entity.
> > >
> > > You don't need a separate VDC to tell you how to get at myfile here:
> > >
> > > file myfile <"gsiftp://terminable.ci.uchicago.edu/scratch/foo/">;
> > >
> > > The 'data file pointer store' exists already - its the hierarchical
> > > namespace that is rooted in IANA's management of the URI and DNS space,
> > > continues to UC's management of DNS space and then down to my management
> > > of terminable's filesystem space and then down to whoever owns the foo
> > > directory.
> > >
> > >
> > > On Sun, 1 Jul 2007, bugzilla-daemon at mcs.anl.gov wrote:
> > >
> > > > http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=76
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ------- Comment #1 from hategan at mcs.anl.gov 2007-07-01 02:18 -------
> > > > This would require a data file pointer store (VDC like thing) which can record
> > > > where intermediate files are instead of assuming they are always available on
> > > > the submit host.
> > > >
> > > >
> > > >
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
> >
> >
>
From benc at hawaga.org.uk Thu Jul 5 11:25:06 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 16:25:06 +0000 (GMT)
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To: <1183644607.5084.9.camel@blabla.mcs.anl.gov>
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
<1183643731.5084.3.camel@blabla.mcs.anl.gov>
<1183644607.5084.9.camel@blabla.mcs.anl.gov>
Message-ID:
they're always in the place that the path name says they are. whether its
a URI or a local relative path.
On Thu, 5 Jul 2007, Mihael Hategan wrote:
> On Thu, 2007-07-05 at 14:05 +0000, Ben Clifford wrote:
> > how does it know where files are now, between jobs?
>
> That's the thing. They're always on localhost.
>
> >
> > On Thu, 5 Jul 2007, Mihael Hategan wrote:
> >
> > > I think you're missing something. You need to remember where the files
> > > are. The mapping information becomes insufficient. It tells you where
> > > some initial files were, but it won't contain any site information. And
> > > that's good, because the decision of where something is done is made at
> > > run-time. But you still need some store (even though probably
> > > memory-based and only persistent through one swift run).
> > >
> > > On Thu, 2007-07-05 at 04:41 +0000, Ben Clifford wrote:
> > > > I don't think that's true.
> > > >
> > > > If data files are labelled with URIs rather than
> > > > paths-relative-to-submit-directory, then those URIs are understandable
> > > > without a VDC-as-entity.
> > > >
> > > > You don't need a separate VDC to tell you how to get at myfile here:
> > > >
> > > > file myfile <"gsiftp://terminable.ci.uchicago.edu/scratch/foo/">;
> > > >
> > > > The 'data file pointer store' exists already - its the hierarchical
> > > > namespace that is rooted in IANA's management of the URI and DNS space,
> > > > continues to UC's management of DNS space and then down to my management
> > > > of terminable's filesystem space and then down to whoever owns the foo
> > > > directory.
> > > >
> > > >
> > > > On Sun, 1 Jul 2007, bugzilla-daemon at mcs.anl.gov wrote:
> > > >
> > > > > http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=76
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ------- Comment #1 from hategan at mcs.anl.gov 2007-07-01 02:18 -------
> > > > > This would require a data file pointer store (VDC like thing) which can record
> > > > > where intermediate files are instead of assuming they are always available on
> > > > > the submit host.
> > > > >
> > > > >
> > > > >
> > > > _______________________________________________
> > > > Swift-devel mailing list
> > > > Swift-devel at ci.uchicago.edu
> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > > >
> > >
> > >
> >
>
>
From hategan at mcs.anl.gov Thu Jul 5 11:41:30 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Thu, 05 Jul 2007 11:41:30 -0500
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To:
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
<1183643731.5084.3.camel@blabla.mcs.anl.gov>
<1183644607.5084.9.camel@blabla.mcs.anl.gov>
Message-ID: <1183653690.11132.2.camel@blabla.mcs.anl.gov>
On Thu, 2007-07-05 at 16:25 +0000, Ben Clifford wrote:
> they're always in the place that the path name says they are. whether its
> a URI or a local relative path.
Right, but whereas in the current scheme you can assume the site is
localhost, because files are always staged back to localhost, if you
don't do the stage-out, that assumption goes away. In that case, the
site information needs to be recorded.
>
> On Thu, 5 Jul 2007, Mihael Hategan wrote:
>
> > On Thu, 2007-07-05 at 14:05 +0000, Ben Clifford wrote:
> > > how does it know where files are now, between jobs?
> >
> > That's the thing. They're always on localhost.
> >
> > >
> > > On Thu, 5 Jul 2007, Mihael Hategan wrote:
> > >
> > > > I think you're missing something. You need to remember where the files
> > > > are. The mapping information becomes insufficient. It tells you where
> > > > some initial files were, but it won't contain any site information. And
> > > > that's good, because the decision of where something is done is made at
> > > > run-time. But you still need some store (even though probably
> > > > memory-based and only persistent through one swift run).
> > > >
> > > > On Thu, 2007-07-05 at 04:41 +0000, Ben Clifford wrote:
> > > > > I don't think that's true.
> > > > >
> > > > > If data files are labelled with URIs rather than
> > > > > paths-relative-to-submit-directory, then those URIs are understandable
> > > > > without a VDC-as-entity.
> > > > >
> > > > > You don't need a separate VDC to tell you how to get at myfile here:
> > > > >
> > > > > file myfile <"gsiftp://terminable.ci.uchicago.edu/scratch/foo/">;
> > > > >
> > > > > The 'data file pointer store' exists already - its the hierarchical
> > > > > namespace that is rooted in IANA's management of the URI and DNS space,
> > > > > continues to UC's management of DNS space and then down to my management
> > > > > of terminable's filesystem space and then down to whoever owns the foo
> > > > > directory.
> > > > >
> > > > >
> > > > > On Sun, 1 Jul 2007, bugzilla-daemon at mcs.anl.gov wrote:
> > > > >
> > > > > > http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=76
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ------- Comment #1 from hategan at mcs.anl.gov 2007-07-01 02:18 -------
> > > > > > This would require a data file pointer store (VDC like thing) which can record
> > > > > > where intermediate files are instead of assuming they are always available on
> > > > > > the submit host.
> > > > > >
> > > > > >
> > > > > >
> > > > > _______________________________________________
> > > > > Swift-devel mailing list
> > > > > Swift-devel at ci.uchicago.edu
> > > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > > > >
> > > >
> > > >
> > >
> >
> >
>
From benc at hawaga.org.uk Thu Jul 5 11:47:45 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 16:47:45 +0000 (GMT)
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To: <1183653690.11132.2.camel@blabla.mcs.anl.gov>
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
<1183643731.5084.3.camel@blabla.mcs.anl.gov>
<1183644607.5084.9.camel@blabla.mcs.anl.gov>
<1183653690.11132.2.camel@blabla.mcs.anl.gov>
Message-ID:
right.
On Thu, 5 Jul 2007, Mihael Hategan wrote:
> On Thu, 2007-07-05 at 16:25 +0000, Ben Clifford wrote:
> > they're always in the place that the path name says they are. whether its
> > a URI or a local relative path.
>
> Right, but whereas in the current scheme you can assume the site is
> localhost, because files are always staged back to localhost, if you
> don't do the stage-out, that assumption goes away. In that case, the
> site information needs to be recorded.
>
> >
> > On Thu, 5 Jul 2007, Mihael Hategan wrote:
> >
> > > On Thu, 2007-07-05 at 14:05 +0000, Ben Clifford wrote:
> > > > how does it know where files are now, between jobs?
> > >
> > > That's the thing. They're always on localhost.
> > >
> > > >
> > > > On Thu, 5 Jul 2007, Mihael Hategan wrote:
> > > >
> > > > > I think you're missing something. You need to remember where the files
> > > > > are. The mapping information becomes insufficient. It tells you where
> > > > > some initial files were, but it won't contain any site information. And
> > > > > that's good, because the decision of where something is done is made at
> > > > > run-time. But you still need some store (even though probably
> > > > > memory-based and only persistent through one swift run).
> > > > >
> > > > > On Thu, 2007-07-05 at 04:41 +0000, Ben Clifford wrote:
> > > > > > I don't think that's true.
> > > > > >
> > > > > > If data files are labelled with URIs rather than
> > > > > > paths-relative-to-submit-directory, then those URIs are understandable
> > > > > > without a VDC-as-entity.
> > > > > >
> > > > > > You don't need a separate VDC to tell you how to get at myfile here:
> > > > > >
> > > > > > file myfile <"gsiftp://terminable.ci.uchicago.edu/scratch/foo/">;
> > > > > >
> > > > > > The 'data file pointer store' exists already - its the hierarchical
> > > > > > namespace that is rooted in IANA's management of the URI and DNS space,
> > > > > > continues to UC's management of DNS space and then down to my management
> > > > > > of terminable's filesystem space and then down to whoever owns the foo
> > > > > > directory.
> > > > > >
> > > > > >
> > > > > > On Sun, 1 Jul 2007, bugzilla-daemon at mcs.anl.gov wrote:
> > > > > >
> > > > > > > http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=76
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ------- Comment #1 from hategan at mcs.anl.gov 2007-07-01 02:18 -------
> > > > > > > This would require a data file pointer store (VDC like thing) which can record
> > > > > > > where intermediate files are instead of assuming they are always available on
> > > > > > > the submit host.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > _______________________________________________
> > > > > > Swift-devel mailing list
> > > > > > Swift-devel at ci.uchicago.edu
> > > > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
>
>
From benc at hawaga.org.uk Thu Jul 5 11:55:26 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 16:55:26 +0000 (GMT)
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To: <1183644607.5084.9.camel@blabla.mcs.anl.gov>
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
<1183643731.5084.3.camel@blabla.mcs.anl.gov>
<1183644607.5084.9.camel@blabla.mcs.anl.gov>
Message-ID:
so I was thinking the other day while poking through code.
'data' in SwiftScript terms is mostly represented by DSHandle objects.
such objects (which can have one of several implementing classes, and
potentially more in future) have a number of properties, such as:
. value - what the 'value' is, for adding to other values, using @strcat
on, performing array/member access using [] and .
. submit-side location - what is extracted with @filename and used when
that 'data' is passed to an application rather than being operated on by
submit-side functions.
Neither of these are compulsory (and I think in practice at the moment it
works out that you either have a filename or a value and never
meaningfully both).
So a different model of mapping (which might work better when we want data
that doesn't necessarily exist as discrete files or as in-memory values -
the two examples that I've seen talked about are 'data from an sql
database' and 'constants in a csv file') might be that mappers generate
DSHandle trees (specifically a mapper generates a DSHandle, which might
have descendants). Those DSHandles might have values, might have
filenames, might have other attributes, might have ongoing annotation
(which could include keeping track of where within-this-run copies have
been made).
--
From yongzh at cs.uchicago.edu Thu Jul 5 12:14:32 2007
From: yongzh at cs.uchicago.edu (Yong Zhao)
Date: Thu, 5 Jul 2007 12:14:32 -0500 (CDT)
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To:
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
<1183643731.5084.3.camel@blabla.mcs.anl.gov>
<1183644607.5084.9.camel@blabla.mcs.anl.gov>
Message-ID:
My original thinking about value/filename was that we don't distinguish
those at the logical level, essentially they could all just be values.
Then when we need to call mapper functions (getFilename, for instance), we
interprete the values differently. So in the case of getFilename, we can
interprete the value either as
1) the filename itself, returning the value directly
2) writing the value into a file, and returning an automatically generated
filename.
3) some other possibilities, e.g. a directory of files.
The current DSHandle interface does allow nested trees, so a mapper
could return a dshandle tree as the implementation currently stands.
Yong.
On Thu, 5 Jul 2007, Ben Clifford wrote:
>
> so I was thinking the other day while poking through code.
>
> 'data' in SwiftScript terms is mostly represented by DSHandle objects.
>
> such objects (which can have one of several implementing classes, and
> potentially more in future) have a number of properties, such as:
>
> . value - what the 'value' is, for adding to other values, using @strcat
> on, performing array/member access using [] and .
>
> . submit-side location - what is extracted with @filename and used when
> that 'data' is passed to an application rather than being operated on by
> submit-side functions.
>
> Neither of these are compulsory (and I think in practice at the moment it
> works out that you either have a filename or a value and never
> meaningfully both).
>
> So a different model of mapping (which might work better when we want data
> that doesn't necessarily exist as discrete files or as in-memory values -
> the two examples that I've seen talked about are 'data from an sql
> database' and 'constants in a csv file') might be that mappers generate
> DSHandle trees (specifically a mapper generates a DSHandle, which might
> have descendants). Those DSHandles might have values, might have
> filenames, might have other attributes, might have ongoing annotation
> (which could include keeping track of where within-this-run copies have
> been made).
>
> --
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From benc at hawaga.org.uk Thu Jul 5 12:22:25 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 17:22:25 +0000 (GMT)
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To:
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
<1183643731.5084.3.camel@blabla.mcs.anl.gov>
<1183644607.5084.9.camel@blabla.mcs.anl.gov>
Message-ID:
On Thu, 5 Jul 2007, Yong Zhao wrote:
> My original thinking about value/filename was that we don't distinguish
> those at the logical level, essentially they could all just be values.
> Then when we need to call mapper functions (getFilename, for instance), we
> interprete the values differently. So in the case of getFilename, we can
> interprete the value either as
> 1) the filename itself, returning the value directly
> 2) writing the value into a file, and returning an automatically generated
> filename.
> 3) some other possibilities, e.g. a directory of files.
option 1 goes against the strongly typed model - if I have a brain image,
I dont want an access to that brain image to suddenly be the string
"brain.img" - that isn't of type 'braingimage', its of type 'string'.
but the other two options work, I think - that's what a mapper does -
expresses how swiftscript data is interpreted in various different ways
- as a (set of) file(s), as a in-memory value, in some other form.
But I don't think it will always be the case that each data object will be
accessible in each form. For example, a brain scan doesn't make much sense
being mapepd into the karajan runtime at the moment - we have nothing to
do interesting things with such.
>
> The current DSHandle interface does allow nested trees, so a mapper
> could return a dshandle tree as the implementation currently stands.
>
> Yong.
>
>
> On Thu, 5 Jul 2007, Ben Clifford wrote:
>
> >
> > so I was thinking the other day while poking through code.
> >
> > 'data' in SwiftScript terms is mostly represented by DSHandle objects.
> >
> > such objects (which can have one of several implementing classes, and
> > potentially more in future) have a number of properties, such as:
> >
> > . value - what the 'value' is, for adding to other values, using @strcat
> > on, performing array/member access using [] and .
> >
> > . submit-side location - what is extracted with @filename and used when
> > that 'data' is passed to an application rather than being operated on by
> > submit-side functions.
> >
> > Neither of these are compulsory (and I think in practice at the moment it
> > works out that you either have a filename or a value and never
> > meaningfully both).
> >
> > So a different model of mapping (which might work better when we want data
> > that doesn't necessarily exist as discrete files or as in-memory values -
> > the two examples that I've seen talked about are 'data from an sql
> > database' and 'constants in a csv file') might be that mappers generate
> > DSHandle trees (specifically a mapper generates a DSHandle, which might
> > have descendants). Those DSHandles might have values, might have
> > filenames, might have other attributes, might have ongoing annotation
> > (which could include keeping track of where within-this-run copies have
> > been made).
> >
> > --
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
>
>
From yongzh at cs.uchicago.edu Thu Jul 5 12:28:36 2007
From: yongzh at cs.uchicago.edu (Yong Zhao)
Date: Thu, 5 Jul 2007 12:28:36 -0500 (CDT)
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To:
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
<1183643731.5084.3.camel@blabla.mcs.anl.gov>
<1183644607.5084.9.camel@blabla.mcs.anl.gov>
Message-ID:
option 1) does not say it is of type string, but it is of type any, which
means it could be an opaque file that we are not interested in going into
the file content, in which case, a file name could be in place of the
content, it all depends on how the mapper interprete the value.
Yong.
On Thu, 5 Jul 2007, Ben Clifford wrote:
>
>
> On Thu, 5 Jul 2007, Yong Zhao wrote:
>
> > My original thinking about value/filename was that we don't distinguish
> > those at the logical level, essentially they could all just be values.
> > Then when we need to call mapper functions (getFilename, for instance), we
> > interprete the values differently. So in the case of getFilename, we can
> > interprete the value either as
> > 1) the filename itself, returning the value directly
>
> > 2) writing the value into a file, and returning an automatically generated
> > filename.
>
> > 3) some other possibilities, e.g. a directory of files.
>
> option 1 goes against the strongly typed model - if I have a brain image,
> I dont want an access to that brain image to suddenly be the string
> "brain.img" - that isn't of type 'braingimage', its of type 'string'.
>
> but the other two options work, I think - that's what a mapper does -
> expresses how swiftscript data is interpreted in various different ways
> - as a (set of) file(s), as a in-memory value, in some other form.
>
> But I don't think it will always be the case that each data object will be
> accessible in each form. For example, a brain scan doesn't make much sense
> being mapepd into the karajan runtime at the moment - we have nothing to
> do interesting things with such.
>
> >
> > The current DSHandle interface does allow nested trees, so a mapper
> > could return a dshandle tree as the implementation currently stands.
> >
> > Yong.
> >
> >
> > On Thu, 5 Jul 2007, Ben Clifford wrote:
> >
> > >
> > > so I was thinking the other day while poking through code.
> > >
> > > 'data' in SwiftScript terms is mostly represented by DSHandle objects.
> > >
> > > such objects (which can have one of several implementing classes, and
> > > potentially more in future) have a number of properties, such as:
> > >
> > > . value - what the 'value' is, for adding to other values, using @strcat
> > > on, performing array/member access using [] and .
> > >
> > > . submit-side location - what is extracted with @filename and used when
> > > that 'data' is passed to an application rather than being operated on by
> > > submit-side functions.
> > >
> > > Neither of these are compulsory (and I think in practice at the moment it
> > > works out that you either have a filename or a value and never
> > > meaningfully both).
> > >
> > > So a different model of mapping (which might work better when we want data
> > > that doesn't necessarily exist as discrete files or as in-memory values -
> > > the two examples that I've seen talked about are 'data from an sql
> > > database' and 'constants in a csv file') might be that mappers generate
> > > DSHandle trees (specifically a mapper generates a DSHandle, which might
> > > have descendants). Those DSHandles might have values, might have
> > > filenames, might have other attributes, might have ongoing annotation
> > > (which could include keeping track of where within-this-run copies have
> > > been made).
> > >
> > > --
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
> >
> >
>
From hategan at mcs.anl.gov Thu Jul 5 13:02:03 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Thu, 05 Jul 2007 13:02:03 -0500
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To:
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
<1183643731.5084.3.camel@blabla.mcs.anl.gov>
<1183644607.5084.9.camel@blabla.mcs.anl.gov>
Message-ID: <1183658523.13928.3.camel@blabla.mcs.anl.gov>
On Thu, 2007-07-05 at 16:55 +0000, Ben Clifford wrote:
> So a different model of mapping (which might work better when we want data
> that doesn't necessarily exist as discrete files or as in-memory values -
> the two examples that I've seen talked about are 'data from an sql
> database' and 'constants in a csv file') might be that mappers generate
> DSHandle trees (specifically a mapper generates a DSHandle, which might
> have descendants). Those DSHandles might have values, might have
> filenames, might have other attributes, might have ongoing annotation
> (which could include keeping track of where within-this-run copies have
> been made).
However, we should keep in mind that mapping is lazy. We want that to
achieve scalability, and at least in theory, infinite arrays (for that
we would need some form of garbage collection).
On the other hand, data itself is future-like. The difference being that
everything is computed as soon as possible, but access is delayed until
data is available.
>
> --
>
From hategan at mcs.anl.gov Thu Jul 5 13:05:45 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Thu, 05 Jul 2007 13:05:45 -0500
Subject: [Swift-devel] [Bug 76] disable intermediate stageout of data
In-Reply-To:
References: <20070701071846.56FF016505@foxtrot.mcs.anl.gov>
<1183643731.5084.3.camel@blabla.mcs.anl.gov>
<1183644607.5084.9.camel@blabla.mcs.anl.gov>
Message-ID: <1183658745.13928.8.camel@blabla.mcs.anl.gov>
On Thu, 2007-07-05 at 12:14 -0500, Yong Zhao wrote:
> My original thinking about value/filename was that we don't distinguish
> those at the logical level, essentially they could all just be values.
> Then when we need to call mapper functions (getFilename, for instance), we
> interprete the values differently. So in the case of getFilename, we can
> interprete the value either as
> 1) the filename itself, returning the value directly
> 2) writing the value into a file, and returning an automatically generated
> filename.
> 3) some other possibilities, e.g. a directory of files.
This clearly conflicts with the ability to apply swift functions to data
in files or databases, as one would need, in the case of files, both a
file pointer and actual data.
I would rather follow a known model for this: pointers. There are
addresses (files, uris, db/table/column/row) and values, which are
stored at those addresses. What's missing from the scheme right now is
the ability of a mapper to fetch actual data from such locations when
needed.
>
> The current DSHandle interface does allow nested trees, so a mapper
> could return a dshandle tree as the implementation currently stands.
>
> Yong.
>
>
> On Thu, 5 Jul 2007, Ben Clifford wrote:
>
> >
> > so I was thinking the other day while poking through code.
> >
> > 'data' in SwiftScript terms is mostly represented by DSHandle objects.
> >
> > such objects (which can have one of several implementing classes, and
> > potentially more in future) have a number of properties, such as:
> >
> > . value - what the 'value' is, for adding to other values, using @strcat
> > on, performing array/member access using [] and .
> >
> > . submit-side location - what is extracted with @filename and used when
> > that 'data' is passed to an application rather than being operated on by
> > submit-side functions.
> >
> > Neither of these are compulsory (and I think in practice at the moment it
> > works out that you either have a filename or a value and never
> > meaningfully both).
> >
> > So a different model of mapping (which might work better when we want data
> > that doesn't necessarily exist as discrete files or as in-memory values -
> > the two examples that I've seen talked about are 'data from an sql
> > database' and 'constants in a csv file') might be that mappers generate
> > DSHandle trees (specifically a mapper generates a DSHandle, which might
> > have descendants). Those DSHandles might have values, might have
> > filenames, might have other attributes, might have ongoing annotation
> > (which could include keeping track of where within-this-run copies have
> > been made).
> >
> > --
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
>
From nefedova at mcs.anl.gov Thu Jul 5 13:55:51 2007
From: nefedova at mcs.anl.gov (Veronika Nefedova)
Date: Thu, 5 Jul 2007 13:55:51 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To: <1183429417.16404.0.camel@blabla.mcs.anl.gov>
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
Message-ID:
my workflow doesn't work with recent changes. It worked fine for 1
molecule, but fails for 244 (right after compilation step, before
submitting it to the grid). These are the errors:
2007-07-05 13:37:51,294 DEBUG VDL2ExecutionContext Missing argument
s11 for sys:element(out1, out2, out3, out4, in1, in2, in3, in4, in5,
in6, in7, in8, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11)
Missing argument s11 for sys:element(out1, out2, out3, out4, in1,
in2, in3, in4, in5, in6, in7, in8, s1, s2, s3, s4, s5, s6, s7, s8,
s9, s10, s11)
CHARMM3 @ MolDyn-244.kml, line: 209
vdl:mains @ MolDyn-244.kml, line: 583910
at
org.globus.cog.karajan.workflow.nodes.user.UserDefinedElement.prepareIns
tanceArguments(UserDefinedElement.java:196)
at
org.globus.cog.karajan.workflow.nodes.user.UserDefinedElement.startBody(
UserDefinedElement.java:170)
at
org.globus.cog.karajan.workflow.nodes.user.SequentialImplicitExecutionUD
E.startBody(SequentialImplicitExecutionUDE.java:55)
at
org.globus.cog.karajan.workflow.nodes.user.SequentialImplicitExecutionUD
E.childCompleted(SequentialImplicitExecutionUDE.java:82)
at
org.globus.cog.karajan.workflow.nodes.Sequential.notificationEvent
(Sequential.java:33)
at org.globus.cog.karajan.workflow.nodes.FlowNode.event
(FlowNode.java:334)
at org.globus.cog.karajan.workflow.events.EventBus.send
(EventBus.java:123)
at org.globus.cog.karajan.workflow.events.EventBus.sendHooked
(EventBus.java:97)
at
org.globus.cog.karajan.workflow.nodes.FlowNode.fireNotificationEvent
(FlowNode.java:172)
at org.globus.cog.karajan.workflow.nodes.FlowNode.complete
(FlowNode.java:298)
at org.globus.cog.karajan.workflow.nodes.FlowContainer.post
(FlowContainer.java:58)
at
org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArguments.ch
ildCompleted(AbstractSequentialWithArguments.java:192)
at
org.globus.cog.karajan.workflow.nodes.Sequential.notificationEvent
(Sequential.java:33)
at org.globus.cog.karajan.workflow.nodes.FlowNode.event
(FlowNode.java:334)
at org.globus.cog.karajan.workflow.events.EventBus.send
(EventBus.java:123)
at org.globus.cog.karajan.workflow.events.EventBus.sendHooked
(EventBus.java:97)
at
org.globus.cog.karajan.workflow.nodes.FlowNode.fireNotificationEvent
(FlowNode.java:172)
at org.globus.cog.karajan.workflow.nodes.FlowNode.complete
(FlowNode.java:298)
at org.globus.cog.karajan.workflow.nodes.FlowContainer.post
(FlowContainer.java:58)
at
org.globus.cog.karajan.workflow.nodes.Parallel.notificationEvent
(Parallel.java:90)
at org.globus.cog.karajan.workflow.nodes.FlowNode.event
(FlowNode.java:334)
a complete log is on terminable in ~nefedova/MolDyn-244-
zvhy3me4scm61.log
the MolDyn-244.* files are also there. Please note that this is
exactly the same file (dtm) that worked before.
Nika
On Jul 2, 2007, at 9:23 PM, Mihael Hategan wrote:
> Yup. Try now.
>
> On Tue, 2007-07-03 at 06:38 +0530, Ben Clifford wrote:
>> I get the below when I try to run a hello world workflow
>> (examples/tutorial/q1.swift).
>>
>> I think Nika also saw something that looks similar, with a different
>> workflow.
>>
>> This is with cog r1655.
>>
>> I reverted my checkout to cog r1650 (svn merge -r1655:1650 .) and
>> hello
>> world runs ok (r1650 being before the most recent set of cog
>> commits).
>>
>>
>> $ swift -debug q1.swift
>> Recompilation suppressed.
>>
>> null
>> kernel:cache @ sys.xml, line: 3
>> Caused by: java.lang.UnsupportedOperationException
>> at java.util.AbstractMap.put(AbstractMap.java:228)
>> at
>> org.globus.cog.karajan.workflow.nodes.CacheNode.getTrackingArguments(
>> CacheNode.java:153)
>> at
>> org.globus.cog.karajan.workflow.nodes.CacheNode.post
>> (CacheNode.java:77)
>> at
>> org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArguments
>> .childCompleted(AbstractSequentialWithArguments.java:192)
>> at
>> org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.nonAr
>> gChildCompleted(PartialArgumentsContainer.java:90)
>> at
>> org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.child
>> Completed(PartialArgumentsContainer.java:85)
>> at
>> org.globus.cog.karajan.workflow.nodes.Sequential.notificationEvent
>> (Sequential.java:33)
>> at
>> org.globus.cog.karajan.workflow.nodes.CacheNode.notificationEvent
>> (CacheNode.java:111)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowNode.event(FlowNode.java:
>> 334)
>> at
>> org.globus.cog.karajan.workflow.events.EventBus.send(EventBus.java:
>> 123)
>> at
>> org.globus.cog.karajan.workflow.events.EventBus.sendHooked
>> (EventBus.java:97)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowNode.fireNotificationEvent(
>> FlowNode.java:172)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowNode.complete
>> (FlowNode.java:298)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowContainer.post
>> (FlowContainer.java:58)
>> at
>> org.globus.cog.karajan.workflow.nodes.Namespace.post
>> (Namespace.java:40)
>> at
>> org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArguments
>> .childCompleted(AbstractSequentialWithArguments.java:192)
>> at
>> org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.nonAr
>> gChildCompleted(PartialArgumentsContainer.java:90)
>>
>>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From benc at hawaga.org.uk Thu Jul 5 14:57:25 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 19:57:25 +0000 (GMT)
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
Message-ID:
ou have your heap set on the 244 molecule workflow? I run out at the
compile stage with default.
--
From nefedova at mcs.anl.gov Thu Jul 5 15:01:06 2007
From: nefedova at mcs.anl.gov (Veronika Nefedova)
Date: Thu, 5 Jul 2007 15:01:06 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
Message-ID:
yep, its set to the max:
OPTIONS="-Xms1536m -Xmx1536m"
(in bin/swift )
On Jul 5, 2007, at 2:57 PM, Ben Clifford wrote:
> ou have your heap set on the 244 molecule workflow? I run out at the
> compile stage with default.
> --
>
>
From benc at hawaga.org.uk Thu Jul 5 14:39:32 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 19:39:32 +0000 (GMT)
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
Message-ID:
did you touch both the 1 molecule and 244 moleule .swift files to cause
recompilation?
also, do you have the 1-molecule .swift, .xml and .kml files around?
On Thu, 5 Jul 2007, Veronika Nefedova wrote:
> my workflow doesn't work with recent changes. It worked fine for 1 molecule,
> but fails for 244 (right after compilation step, before submitting it to the
> grid). These are the errors:
>
> 2007-07-05 13:37:51,294 DEBUG VDL2ExecutionContext Missing argument s11 for
> sys:element(out1, out2, out3, out4, in1, in2, in3, in4, in5, in6, in7, in8,
> s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11)
> Missing argument s11 for sys:element(out1, out2, out3, out4, in1, in2, in3,
> in4, in5, in6, in7, in8, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11)
> CHARMM3 @ MolDyn-244.kml, line: 209
> vdl:mains @ MolDyn-244.kml, line: 583910
>
> at
> org.globus.cog.karajan.workflow.nodes.user.UserDefinedElement.prepareInstanceArguments(UserDefinedElement.java:196)
> at
> org.globus.cog.karajan.workflow.nodes.user.UserDefinedElement.startBody(UserDefinedElement.java:170)
> at
> org.globus.cog.karajan.workflow.nodes.user.SequentialImplicitExecutionUDE.startBody(SequentialImplicitExecutionUDE.java:55)
> at
> org.globus.cog.karajan.workflow.nodes.user.SequentialImplicitExecutionUDE.childCompleted(SequentialImplicitExecutionUDE.java:82)
> at
> org.globus.cog.karajan.workflow.nodes.Sequential.notificationEvent(Sequential.java:33)
> at
> org.globus.cog.karajan.workflow.nodes.FlowNode.event(FlowNode.java:334)
> at
> org.globus.cog.karajan.workflow.events.EventBus.send(EventBus.java:123)
> at
> org.globus.cog.karajan.workflow.events.EventBus.sendHooked(EventBus.java:97)
> at
> org.globus.cog.karajan.workflow.nodes.FlowNode.fireNotificationEvent(FlowNode.java:172)
> at
> org.globus.cog.karajan.workflow.nodes.FlowNode.complete(FlowNode.java:298)
> at
> org.globus.cog.karajan.workflow.nodes.FlowContainer.post(FlowContainer.java:58)
> at
> org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArguments.childCompleted(AbstractSequentialWithArguments.java:192)
> at
> org.globus.cog.karajan.workflow.nodes.Sequential.notificationEvent(Sequential.java:33)
> at
> org.globus.cog.karajan.workflow.nodes.FlowNode.event(FlowNode.java:334)
> at
> org.globus.cog.karajan.workflow.events.EventBus.send(EventBus.java:123)
> at
> org.globus.cog.karajan.workflow.events.EventBus.sendHooked(EventBus.java:97)
> at
> org.globus.cog.karajan.workflow.nodes.FlowNode.fireNotificationEvent(FlowNode.java:172)
> at
> org.globus.cog.karajan.workflow.nodes.FlowNode.complete(FlowNode.java:298)
> at
> org.globus.cog.karajan.workflow.nodes.FlowContainer.post(FlowContainer.java:58)
> at
> org.globus.cog.karajan.workflow.nodes.Parallel.notificationEvent(Parallel.java:90)
> at
> org.globus.cog.karajan.workflow.nodes.FlowNode.event(FlowNode.java:334)
>
>
> a complete log is on terminable in ~nefedova/MolDyn-244-zvhy3me4scm61.log
> the MolDyn-244.* files are also there. Please note that this is exactly the
> same file (dtm) that worked before.
>
> Nika
>
>
> On Jul 2, 2007, at 9:23 PM, Mihael Hategan wrote:
>
> > Yup. Try now.
> >
> > On Tue, 2007-07-03 at 06:38 +0530, Ben Clifford wrote:
> > > I get the below when I try to run a hello world workflow
> > > (examples/tutorial/q1.swift).
> > >
> > > I think Nika also saw something that looks similar, with a different
> > > workflow.
> > >
> > > This is with cog r1655.
> > >
> > > I reverted my checkout to cog r1650 (svn merge -r1655:1650 .) and hello
> > > world runs ok (r1650 being before the most recent set of cog commits).
> > >
> > >
> > > $ swift -debug q1.swift
> > > Recompilation suppressed.
> > >
> > > null
> > > kernel:cache @ sys.xml, line: 3
> > > Caused by: java.lang.UnsupportedOperationException
> > > at java.util.AbstractMap.put(AbstractMap.java:228)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.CacheNode.getTrackingArguments(CacheNode.java:153)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.CacheNode.post(CacheNode.java:77)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArguments.childCompleted(AbstractSequentialWithArguments.java:192)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.nonArgChildCompleted(PartialArgumentsContainer.java:90)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.childCompleted(PartialArgumentsContainer.java:85)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.Sequential.notificationEvent(Sequential.java:33)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.CacheNode.notificationEvent(CacheNode.java:111)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.FlowNode.event(FlowNode.java:334)
> > > at
> > > org.globus.cog.karajan.workflow.events.EventBus.send(EventBus.java:123)
> > > at
> > > org.globus.cog.karajan.workflow.events.EventBus.sendHooked(EventBus.java:97)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.FlowNode.fireNotificationEvent(FlowNode.java:172)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.FlowNode.complete(FlowNode.java:298)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.FlowContainer.post(FlowContainer.java:58)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.Namespace.post(Namespace.java:40)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArguments.childCompleted(AbstractSequentialWithArguments.java:192)
> > > at
> > > org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.nonArgChildCompleted(PartialArgumentsContainer.java:90)
> > >
> > >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
>
From nefedova at mcs.anl.gov Thu Jul 5 15:03:28 2007
From: nefedova at mcs.anl.gov (Veronika Nefedova)
Date: Thu, 5 Jul 2007 15:03:28 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
Message-ID:
you can use my kml file that I compiled today with the latest karajan
(its on terminable).
On Jul 5, 2007, at 2:57 PM, Ben Clifford wrote:
> ou have your heap set on the 244 molecule workflow? I run out at the
> compile stage with default.
> --
>
>
From nefedova at mcs.anl.gov Thu Jul 5 15:06:07 2007
From: nefedova at mcs.anl.gov (Veronika Nefedova)
Date: Thu, 5 Jul 2007 15:06:07 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
Message-ID: <3EF6AA08-FA79-430C-99BE-9CB8EF8CEF70@mcs.anl.gov>
yep, I "touched" them both.
I put the MoDyn-1.* files also in ~nefedova on terminable.
MolDyn-1.dtm ran successfully today.
Nika
On Jul 5, 2007, at 2:39 PM, Ben Clifford wrote:
> did you touch both the 1 molecule and 244 moleule .swift files to
> cause
> recompilation?
>
> also, do you have the 1-molecule .swift, .xml and .kml files around?
>
> On Thu, 5 Jul 2007, Veronika Nefedova wrote:
>
>> my workflow doesn't work with recent changes. It worked fine for 1
>> molecule,
>> but fails for 244 (right after compilation step, before submitting
>> it to the
>> grid). These are the errors:
>>
>> 2007-07-05 13:37:51,294 DEBUG VDL2ExecutionContext Missing
>> argument s11 for
>> sys:element(out1, out2, out3, out4, in1, in2, in3, in4, in5, in6,
>> in7, in8,
>> s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11)
>> Missing argument s11 for sys:element(out1, out2, out3, out4, in1,
>> in2, in3,
>> in4, in5, in6, in7, in8, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10,
>> s11)
>> CHARMM3 @ MolDyn-244.kml, line: 209
>> vdl:mains @ MolDyn-244.kml, line: 583910
>>
>> at
>> org.globus.cog.karajan.workflow.nodes.user.UserDefinedElement.prepare
>> InstanceArguments(UserDefinedElement.java:196)
>> at
>> org.globus.cog.karajan.workflow.nodes.user.UserDefinedElement.startBo
>> dy(UserDefinedElement.java:170)
>> at
>> org.globus.cog.karajan.workflow.nodes.user.SequentialImplicitExecutio
>> nUDE.startBody(SequentialImplicitExecutionUDE.java:55)
>> at
>> org.globus.cog.karajan.workflow.nodes.user.SequentialImplicitExecutio
>> nUDE.childCompleted(SequentialImplicitExecutionUDE.java:82)
>> at
>> org.globus.cog.karajan.workflow.nodes.Sequential.notificationEvent
>> (Sequential.java:33)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowNode.event(FlowNode.java:
>> 334)
>> at
>> org.globus.cog.karajan.workflow.events.EventBus.send(EventBus.java:
>> 123)
>> at
>> org.globus.cog.karajan.workflow.events.EventBus.sendHooked
>> (EventBus.java:97)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowNode.fireNotificationEvent(
>> FlowNode.java:172)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowNode.complete
>> (FlowNode.java:298)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowContainer.post
>> (FlowContainer.java:58)
>> at
>> org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArguments
>> .childCompleted(AbstractSequentialWithArguments.java:192)
>> at
>> org.globus.cog.karajan.workflow.nodes.Sequential.notificationEvent
>> (Sequential.java:33)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowNode.event(FlowNode.java:
>> 334)
>> at
>> org.globus.cog.karajan.workflow.events.EventBus.send(EventBus.java:
>> 123)
>> at
>> org.globus.cog.karajan.workflow.events.EventBus.sendHooked
>> (EventBus.java:97)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowNode.fireNotificationEvent(
>> FlowNode.java:172)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowNode.complete
>> (FlowNode.java:298)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowContainer.post
>> (FlowContainer.java:58)
>> at
>> org.globus.cog.karajan.workflow.nodes.Parallel.notificationEvent
>> (Parallel.java:90)
>> at
>> org.globus.cog.karajan.workflow.nodes.FlowNode.event(FlowNode.java:
>> 334)
>>
>>
>> a complete log is on terminable in ~nefedova/MolDyn-244-
>> zvhy3me4scm61.log
>> the MolDyn-244.* files are also there. Please note that this is
>> exactly the
>> same file (dtm) that worked before.
>>
>> Nika
>>
>>
>> On Jul 2, 2007, at 9:23 PM, Mihael Hategan wrote:
>>
>>> Yup. Try now.
>>>
>>> On Tue, 2007-07-03 at 06:38 +0530, Ben Clifford wrote:
>>>> I get the below when I try to run a hello world workflow
>>>> (examples/tutorial/q1.swift).
>>>>
>>>> I think Nika also saw something that looks similar, with a
>>>> different
>>>> workflow.
>>>>
>>>> This is with cog r1655.
>>>>
>>>> I reverted my checkout to cog r1650 (svn merge -r1655:1650 .)
>>>> and hello
>>>> world runs ok (r1650 being before the most recent set of cog
>>>> commits).
>>>>
>>>>
>>>> $ swift -debug q1.swift
>>>> Recompilation suppressed.
>>>>
>>>> null
>>>> kernel:cache @ sys.xml, line: 3
>>>> Caused by: java.lang.UnsupportedOperationException
>>>> at java.util.AbstractMap.put(AbstractMap.java:228)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.CacheNode.getTrackingArgument
>>>> s(CacheNode.java:153)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.CacheNode.post
>>>> (CacheNode.java:77)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArgumen
>>>> ts.childCompleted(AbstractSequentialWithArguments.java:192)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.non
>>>> ArgChildCompleted(PartialArgumentsContainer.java:90)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.chi
>>>> ldCompleted(PartialArgumentsContainer.java:85)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.Sequential.notificationEvent(
>>>> Sequential.java:33)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.CacheNode.notificationEvent
>>>> (CacheNode.java:111)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.FlowNode.event
>>>> (FlowNode.java:334)
>>>> at
>>>> org.globus.cog.karajan.workflow.events.EventBus.send
>>>> (EventBus.java:123)
>>>> at
>>>> org.globus.cog.karajan.workflow.events.EventBus.sendHooked
>>>> (EventBus.java:97)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.FlowNode.fireNotificationEven
>>>> t(FlowNode.java:172)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.FlowNode.complete
>>>> (FlowNode.java:298)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.FlowContainer.post
>>>> (FlowContainer.java:58)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.Namespace.post
>>>> (Namespace.java:40)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.AbstractSequentialWithArgumen
>>>> ts.childCompleted(AbstractSequentialWithArguments.java:192)
>>>> at
>>>> org.globus.cog.karajan.workflow.nodes.PartialArgumentsContainer.non
>>>> ArgChildCompleted(PartialArgumentsContainer.java:90)
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Swift-devel mailing list
>>> Swift-devel at ci.uchicago.edu
>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>>
>>
>
From benc at hawaga.org.uk Thu Jul 5 15:13:02 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 20:13:02 +0000 (GMT)
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
Message-ID:
what karajan revision? and what swift revision?
(type svn info in the cog and dsk directories...)
On Thu, 5 Jul 2007, Veronika Nefedova wrote:
> you can use my kml file that I compiled today with the latest karajan (its on
> terminable).
>
> On Jul 5, 2007, at 2:57 PM, Ben Clifford wrote:
>
> > ou have your heap set on the 244 molecule workflow? I run out at the
> > compile stage with default.
> > --
> >
> >
>
From nefedova at mcs.anl.gov Thu Jul 5 15:45:49 2007
From: nefedova at mcs.anl.gov (Veronika Nefedova)
Date: Thu, 5 Jul 2007 15:45:49 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
Message-ID: <74CD898E-7A60-4F25-BD15-C0219487AEC0@mcs.anl.gov>
1657 for Karajan and 887 for vdsk
On Jul 5, 2007, at 3:13 PM, Ben Clifford wrote:
>
> what karajan revision? and what swift revision?
>
> (type svn info in the cog and dsk directories...)
>
> On Thu, 5 Jul 2007, Veronika Nefedova wrote:
>
>> you can use my kml file that I compiled today with the latest
>> karajan (its on
>> terminable).
>>
>> On Jul 5, 2007, at 2:57 PM, Ben Clifford wrote:
>>
>>> ou have your heap set on the 244 molecule workflow? I run out at the
>>> compile stage with default.
>>> --
>>>
>>>
>>
>
From hategan at mcs.anl.gov Thu Jul 5 16:20:37 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Thu, 05 Jul 2007 16:20:37 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To: <74CD898E-7A60-4F25-BD15-C0219487AEC0@mcs.anl.gov>
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
<74CD898E-7A60-4F25-BD15-C0219487AEC0@mcs.anl.gov>
Message-ID: <1183670437.31476.0.camel@blabla.mcs.anl.gov>
I might know what it is. Stay tuned.
On Thu, 2007-07-05 at 15:45 -0500, Veronika Nefedova wrote:
> 1657 for Karajan and 887 for vdsk
>
> On Jul 5, 2007, at 3:13 PM, Ben Clifford wrote:
>
> >
> > what karajan revision? and what swift revision?
> >
> > (type svn info in the cog and dsk directories...)
> >
> > On Thu, 5 Jul 2007, Veronika Nefedova wrote:
> >
> >> you can use my kml file that I compiled today with the latest
> >> karajan (its on
> >> terminable).
> >>
> >> On Jul 5, 2007, at 2:57 PM, Ben Clifford wrote:
> >>
> >>> ou have your heap set on the 244 molecule workflow? I run out at the
> >>> compile stage with default.
> >>> --
> >>>
> >>>
> >>
> >
>
From hategan at mcs.anl.gov Thu Jul 5 16:33:42 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Thu, 05 Jul 2007 16:33:42 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To: <1183670437.31476.0.camel@blabla.mcs.anl.gov>
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
<74CD898E-7A60-4F25-BD15-C0219487AEC0@mcs.anl.gov>
<1183670437.31476.0.camel@blabla.mcs.anl.gov>
Message-ID: <1183671222.31476.4.camel@blabla.mcs.anl.gov>
In iteratizing the recursive thing that caused the stack overflow, I
ignored the fact that there was a lock on every object in the recursion
steps.
Tentative fix in SVN. I'm running tests to see if things hold.
On Thu, 2007-07-05 at 16:20 -0500, Mihael Hategan wrote:
> I might know what it is. Stay tuned.
>
> On Thu, 2007-07-05 at 15:45 -0500, Veronika Nefedova wrote:
> > 1657 for Karajan and 887 for vdsk
> >
> > On Jul 5, 2007, at 3:13 PM, Ben Clifford wrote:
> >
> > >
> > > what karajan revision? and what swift revision?
> > >
> > > (type svn info in the cog and dsk directories...)
> > >
> > > On Thu, 5 Jul 2007, Veronika Nefedova wrote:
> > >
> > >> you can use my kml file that I compiled today with the latest
> > >> karajan (its on
> > >> terminable).
> > >>
> > >> On Jul 5, 2007, at 2:57 PM, Ben Clifford wrote:
> > >>
> > >>> ou have your heap set on the 244 molecule workflow? I run out at the
> > >>> compile stage with default.
> > >>> --
> > >>>
> > >>>
> > >>
> > >
> >
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From benc at hawaga.org.uk Thu Jul 5 16:17:54 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 5 Jul 2007 21:17:54 +0000 (GMT)
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To: <74CD898E-7A60-4F25-BD15-C0219487AEC0@mcs.anl.gov>
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
<74CD898E-7A60-4F25-BD15-C0219487AEC0@mcs.anl.gov>
Message-ID:
try r1650 - that's the version of karajan that we've had for ages, before
this week.
--
From nefedova at mcs.anl.gov Thu Jul 5 17:05:43 2007
From: nefedova at mcs.anl.gov (Veronika Nefedova)
Date: Thu, 5 Jul 2007 17:05:43 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
<74CD898E-7A60-4F25-BD15-C0219487AEC0@mcs.anl.gov>
Message-ID: <8DF643EF-54CD-4900-B209-C3C0210D8E8E@mcs.anl.gov>
I know that r1650 works - but I need to use Mihael's fix to see if my
workflow could run successfully w/falcon (thats what his karajan
update is about)
On Jul 5, 2007, at 4:17 PM, Ben Clifford wrote:
>
> try r1650 - that's the version of karajan that we've had for ages,
> before
> this week.
>
> --
>
From hategan at mcs.anl.gov Thu Jul 5 17:10:36 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Thu, 05 Jul 2007 17:10:36 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To: <1183671222.31476.4.camel@blabla.mcs.anl.gov>
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
<74CD898E-7A60-4F25-BD15-C0219487AEC0@mcs.anl.gov>
<1183670437.31476.0.camel@blabla.mcs.anl.gov>
<1183671222.31476.4.camel@blabla.mcs.anl.gov>
Message-ID: <1183673436.9192.0.camel@blabla.mcs.anl.gov>
On Thu, 2007-07-05 at 16:33 -0500, Mihael Hategan wrote:
> Tentative fix in SVN. I'm running tests to see if things hold.
Seems to work, as far as the karajan tests can tell.
>
> On Thu, 2007-07-05 at 16:20 -0500, Mihael Hategan wrote:
> > I might know what it is. Stay tuned.
> >
> > On Thu, 2007-07-05 at 15:45 -0500, Veronika Nefedova wrote:
> > > 1657 for Karajan and 887 for vdsk
> > >
> > > On Jul 5, 2007, at 3:13 PM, Ben Clifford wrote:
> > >
> > > >
> > > > what karajan revision? and what swift revision?
> > > >
> > > > (type svn info in the cog and dsk directories...)
> > > >
> > > > On Thu, 5 Jul 2007, Veronika Nefedova wrote:
> > > >
> > > >> you can use my kml file that I compiled today with the latest
> > > >> karajan (its on
> > > >> terminable).
> > > >>
> > > >> On Jul 5, 2007, at 2:57 PM, Ben Clifford wrote:
> > > >>
> > > >>> ou have your heap set on the 244 molecule workflow? I run out at the
> > > >>> compile stage with default.
> > > >>> --
> > > >>>
> > > >>>
> > > >>
> > > >
> > >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From bugzilla-daemon at mcs.anl.gov Fri Jul 6 09:16:51 2007
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Fri, 6 Jul 2007 09:16:51 -0500 (CDT)
Subject: [Swift-devel] [Bug 72] Campaign for scaling wf up to 244 molecules
In-Reply-To:
Message-ID: <20070706141651.D911516502@foxtrot.mcs.anl.gov>
http://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=72
------- Comment #16 from nefedova at mcs.anl.gov 2007-07-06 09:16 -------
The latest Karajan fix seems to work (i.e. Workflow compiles). Falcon
experiences some problems. Ioan, please post the details of the current
problems here.
Nika
--
Configure bugmail: http://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
From benc at hawaga.org.uk Fri Jul 6 09:49:33 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Fri, 6 Jul 2007 20:19:33 +0530 (IST)
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
Message-ID:
On my machine that seems to take i) forever to compile (as in I gave up
after it generated the 25mb intermediate xml file but before it had made a
kml file), and ii) forever to get to the stage where it tries to execute
anything (as in I gave up before it gave me an error about not being able
to find the transformations to run).
What sort of times does it usually take for you to:
i) compile
ii) run the first executable
?
On Thu, 5 Jul 2007, Ben Clifford wrote:
>
> what karajan revision? and what swift revision?
>
> (type svn info in the cog and dsk directories...)
>
> On Thu, 5 Jul 2007, Veronika Nefedova wrote:
>
> > you can use my kml file that I compiled today with the latest karajan (its on
> > terminable).
> >
> > On Jul 5, 2007, at 2:57 PM, Ben Clifford wrote:
> >
> > > ou have your heap set on the 244 molecule workflow? I run out at the
> > > compile stage with default.
> > > --
> > >
> > >
> >
>
>
From nefedova at mcs.anl.gov Fri Jul 6 10:13:28 2007
From: nefedova at mcs.anl.gov (Veronika Nefedova)
Date: Fri, 6 Jul 2007 10:13:28 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
Message-ID:
with the old version of the script (all loops unrolled) it would take
about 1.5 hours to compile (244 molecules). Once compiled it would
start the execution within a minute.
A new swift code (with the main loop done in 'foreach' is under way
(I am testing it right now).
Nika
On Jul 6, 2007, at 9:49 AM, Ben Clifford wrote:
>
> On my machine that seems to take i) forever to compile (as in I
> gave up
> after it generated the 25mb intermediate xml file but before it had
> made a
> kml file), and ii) forever to get to the stage where it tries to
> execute
> anything (as in I gave up before it gave me an error about not
> being able
> to find the transformations to run).
>
> What sort of times does it usually take for you to:
>
> i) compile
>
> ii) run the first executable
>
> ?
>
> On Thu, 5 Jul 2007, Ben Clifford wrote:
>
>>
>> what karajan revision? and what swift revision?
>>
>> (type svn info in the cog and dsk directories...)
>>
>> On Thu, 5 Jul 2007, Veronika Nefedova wrote:
>>
>>> you can use my kml file that I compiled today with the latest
>>> karajan (its on
>>> terminable).
>>>
>>> On Jul 5, 2007, at 2:57 PM, Ben Clifford wrote:
>>>
>>>> ou have your heap set on the 244 molecule workflow? I run out at
>>>> the
>>>> compile stage with default.
>>>> --
>>>>
>>>>
>>>
>>
>>
>
From hategan at mcs.anl.gov Fri Jul 6 10:16:43 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Fri, 06 Jul 2007 10:16:43 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
Message-ID: <1183735003.9663.0.camel@blabla.mcs.anl.gov>
On Fri, 2007-07-06 at 10:13 -0500, Veronika Nefedova wrote:
> with the old version of the script (all loops unrolled) it would take
> about 1.5 hours to compile (244 molecules). Once compiled it would
> start the execution within a minute.
How can you tell when it's done compiling?
> A new swift code (with the main loop done in 'foreach' is under way
> (I am testing it right now).
>
> Nika
>
> On Jul 6, 2007, at 9:49 AM, Ben Clifford wrote:
>
> >
> > On my machine that seems to take i) forever to compile (as in I
> > gave up
> > after it generated the 25mb intermediate xml file but before it had
> > made a
> > kml file), and ii) forever to get to the stage where it tries to
> > execute
> > anything (as in I gave up before it gave me an error about not
> > being able
> > to find the transformations to run).
> >
> > What sort of times does it usually take for you to:
> >
> > i) compile
> >
> > ii) run the first executable
> >
> > ?
> >
> > On Thu, 5 Jul 2007, Ben Clifford wrote:
> >
> >>
> >> what karajan revision? and what swift revision?
> >>
> >> (type svn info in the cog and dsk directories...)
> >>
> >> On Thu, 5 Jul 2007, Veronika Nefedova wrote:
> >>
> >>> you can use my kml file that I compiled today with the latest
> >>> karajan (its on
> >>> terminable).
> >>>
> >>> On Jul 5, 2007, at 2:57 PM, Ben Clifford wrote:
> >>>
> >>>> ou have your heap set on the 244 molecule workflow? I run out at
> >>>> the
> >>>> compile stage with default.
> >>>> --
> >>>>
> >>>>
> >>>
> >>
> >>
> >
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From nefedova at mcs.anl.gov Fri Jul 6 10:22:23 2007
From: nefedova at mcs.anl.gov (Veronika Nefedova)
Date: Fri, 6 Jul 2007 10:22:23 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To: <1183735003.9663.0.camel@blabla.mcs.anl.gov>
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
<1183735003.9663.0.camel@blabla.mcs.anl.gov>
Message-ID: <8DC8874A-B469-44BA-B9AB-B3CBCBD34E60@mcs.anl.gov>
On Jul 6, 2007, at 10:16 AM, Mihael Hategan wrote:
> On Fri, 2007-07-06 at 10:13 -0500, Veronika Nefedova wrote:
>> with the old version of the script (all loops unrolled) it would take
>> about 1.5 hours to compile (244 molecules). Once compiled it would
>> start the execution within a minute.
>
> How can you tell when it's done compiling?
>
When its done compiling, it starts execution - you right, its hard
to tell when its all done in one step. But when you already have the
compiled code and start execution - it takes less then a minute (30
seconds?) to send the first task out.
Nika
>> A new swift code (with the main loop done in 'foreach' is under way
>> (I am testing it right now).
>>
>> Nika
>>
>> On Jul 6, 2007, at 9:49 AM, Ben Clifford wrote:
>>
>>>
>>> On my machine that seems to take i) forever to compile (as in I
>>> gave up
>>> after it generated the 25mb intermediate xml file but before it had
>>> made a
>>> kml file), and ii) forever to get to the stage where it tries to
>>> execute
>>> anything (as in I gave up before it gave me an error about not
>>> being able
>>> to find the transformations to run).
>>>
>>> What sort of times does it usually take for you to:
>>>
>>> i) compile
>>>
>>> ii) run the first executable
>>>
>>> ?
>>>
>>> On Thu, 5 Jul 2007, Ben Clifford wrote:
>>>
>>>>
>>>> what karajan revision? and what swift revision?
>>>>
>>>> (type svn info in the cog and dsk directories...)
>>>>
>>>> On Thu, 5 Jul 2007, Veronika Nefedova wrote:
>>>>
>>>>> you can use my kml file that I compiled today with the latest
>>>>> karajan (its on
>>>>> terminable).
>>>>>
>>>>> On Jul 5, 2007, at 2:57 PM, Ben Clifford wrote:
>>>>>
>>>>>> ou have your heap set on the 244 molecule workflow? I run out at
>>>>>> the
>>>>>> compile stage with default.
>>>>>> --
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> Swift-devel mailing list
>> Swift-devel at ci.uchicago.edu
>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>
>
From hategan at mcs.anl.gov Fri Jul 6 10:25:32 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Fri, 06 Jul 2007 10:25:32 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To: <8DC8874A-B469-44BA-B9AB-B3CBCBD34E60@mcs.anl.gov>
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
<1183735003.9663.0.camel@blabla.mcs.anl.gov>
<8DC8874A-B469-44BA-B9AB-B3CBCBD34E60@mcs.anl.gov>
Message-ID: <1183735532.10139.0.camel@blabla.mcs.anl.gov>
On Fri, 2007-07-06 at 10:22 -0500, Veronika Nefedova wrote:
> On Jul 6, 2007, at 10:16 AM, Mihael Hategan wrote:
>
> > On Fri, 2007-07-06 at 10:13 -0500, Veronika Nefedova wrote:
> >> with the old version of the script (all loops unrolled) it would take
> >> about 1.5 hours to compile (244 molecules). Once compiled it would
> >> start the execution within a minute.
> >
> > How can you tell when it's done compiling?
> >
>
> When its done compiling, it starts execution - you right, its hard
> to tell when its all done in one step. But when you already have the
> compiled code and start execution - it takes less then a minute (30
> seconds?) to send the first task out.
That makes sense. We need to speed up compilation?
>
> Nika
>
> >> A new swift code (with the main loop done in 'foreach' is under way
> >> (I am testing it right now).
> >>
> >> Nika
> >>
> >> On Jul 6, 2007, at 9:49 AM, Ben Clifford wrote:
> >>
> >>>
> >>> On my machine that seems to take i) forever to compile (as in I
> >>> gave up
> >>> after it generated the 25mb intermediate xml file but before it had
> >>> made a
> >>> kml file), and ii) forever to get to the stage where it tries to
> >>> execute
> >>> anything (as in I gave up before it gave me an error about not
> >>> being able
> >>> to find the transformations to run).
> >>>
> >>> What sort of times does it usually take for you to:
> >>>
> >>> i) compile
> >>>
> >>> ii) run the first executable
> >>>
> >>> ?
> >>>
> >>> On Thu, 5 Jul 2007, Ben Clifford wrote:
> >>>
> >>>>
> >>>> what karajan revision? and what swift revision?
> >>>>
> >>>> (type svn info in the cog and dsk directories...)
> >>>>
> >>>> On Thu, 5 Jul 2007, Veronika Nefedova wrote:
> >>>>
> >>>>> you can use my kml file that I compiled today with the latest
> >>>>> karajan (its on
> >>>>> terminable).
> >>>>>
> >>>>> On Jul 5, 2007, at 2:57 PM, Ben Clifford wrote:
> >>>>>
> >>>>>> ou have your heap set on the 244 molecule workflow? I run out at
> >>>>>> the
> >>>>>> compile stage with default.
> >>>>>> --
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>
> >> _______________________________________________
> >> Swift-devel mailing list
> >> Swift-devel at ci.uchicago.edu
> >> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >>
> >
>
From benc at hawaga.org.uk Fri Jul 6 11:02:01 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Fri, 6 Jul 2007 16:02:01 +0000 (GMT)
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To: <1183735532.10139.0.camel@blabla.mcs.anl.gov>
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
<1183735003.9663.0.camel@blabla.mcs.anl.gov>
<8DC8874A-B469-44BA-B9AB-B3CBCBD34E60@mcs.anl.gov>
<1183735532.10139.0.camel@blabla.mcs.anl.gov>
Message-ID:
On Fri, 6 Jul 2007, Mihael Hategan wrote:
> That makes sense. We need to speed up compilation?
I think more important is concentrating on the langauge features necessary
to have smaller source files.
I'm working with Nika on that at the moment.
--
From hategan at mcs.anl.gov Fri Jul 6 11:05:30 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Fri, 06 Jul 2007 11:05:30 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
<1183735003.9663.0.camel@blabla.mcs.anl.gov>
<8DC8874A-B469-44BA-B9AB-B3CBCBD34E60@mcs.anl.gov>
<1183735532.10139.0.camel@blabla.mcs.anl.gov>
Message-ID: <1183737930.15085.0.camel@blabla.mcs.anl.gov>
On Fri, 2007-07-06 at 16:02 +0000, Ben Clifford wrote:
>
> On Fri, 6 Jul 2007, Mihael Hategan wrote:
>
> > That makes sense. We need to speed up compilation?
>
> I think more important is concentrating on the langauge features necessary
> to have smaller source files.
Yes, of course. But the compilation time is still ridiculous,
considering that it doesn't do much fancy stuff?
>
> I'm working with Nika on that at the moment.
>
From yongzh at cs.uchicago.edu Fri Jul 6 11:14:18 2007
From: yongzh at cs.uchicago.edu (Yong Zhao)
Date: Fri, 6 Jul 2007 11:14:18 -0500 (CDT)
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To: <1183737930.15085.0.camel@blabla.mcs.anl.gov>
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
<1183735003.9663.0.camel@blabla.mcs.anl.gov>
<8DC8874A-B469-44BA-B9AB-B3CBCBD34E60@mcs.anl.gov>
<1183735532.10139.0.camel@blabla.mcs.anl.gov>
<1183737930.15085.0.camel@blabla.mcs.anl.gov>
Message-ID:
I don't think the compilation takes that much time. It is the starting
time from loading the kml file to dispatching the first job that takes a
long time (for 20k jobs).
Yong.
On Fri, 6 Jul 2007, Mihael Hategan wrote:
> On Fri, 2007-07-06 at 16:02 +0000, Ben Clifford wrote:
> >
> > On Fri, 6 Jul 2007, Mihael Hategan wrote:
> >
> > > That makes sense. We need to speed up compilation?
> >
> > I think more important is concentrating on the langauge features necessary
> > to have smaller source files.
>
> Yes, of course. But the compilation time is still ridiculous,
> considering that it doesn't do much fancy stuff?
>
> >
> > I'm working with Nika on that at the moment.
> >
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From benc at hawaga.org.uk Fri Jul 6 11:16:28 2007
From: benc at hawaga.org.uk (Ben Clifford)
Date: Fri, 6 Jul 2007 16:16:28 +0000 (GMT)
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
<1183735003.9663.0.camel@blabla.mcs.anl.gov>
<8DC8874A-B469-44BA-B9AB-B3CBCBD34E60@mcs.anl.gov>
<1183735532.10139.0.camel@blabla.mcs.anl.gov>
<1183737930.15085.0.camel@blabla.mcs.anl.gov>
Message-ID:
the xml->kml conversion took long time when I tried to compile nika's
.swift file.
I can leave it running overnight and see if it ends...
On Fri, 6 Jul 2007, Yong Zhao wrote:
> I don't think the compilation takes that much time. It is the starting
> time from loading the kml file to dispatching the first job that takes a
> long time (for 20k jobs).
>
> Yong.
>
> On Fri, 6 Jul 2007, Mihael Hategan wrote:
>
> > On Fri, 2007-07-06 at 16:02 +0000, Ben Clifford wrote:
> > >
> > > On Fri, 6 Jul 2007, Mihael Hategan wrote:
> > >
> > > > That makes sense. We need to speed up compilation?
> > >
> > > I think more important is concentrating on the langauge features necessary
> > > to have smaller source files.
> >
> > Yes, of course. But the compilation time is still ridiculous,
> > considering that it doesn't do much fancy stuff?
> >
> > >
> > > I'm working with Nika on that at the moment.
> > >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
>
>
From yongzh at cs.uchicago.edu Fri Jul 6 11:19:33 2007
From: yongzh at cs.uchicago.edu (Yong Zhao)
Date: Fri, 6 Jul 2007 11:19:33 -0500 (CDT)
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>
<1183735003.9663.0.camel@blabla.mcs.anl.gov>
<8DC8874A-B469-44BA-B9AB-B3CBCBD34E60@mcs.anl.gov>
<1183735532.10139.0.camel@blabla.mcs.anl.gov>
<1183737930.15085.0.camel@blabla.mcs.anl.gov>
Message-ID:
Really? that is a bit strange. I only tried compiling the 100 molecule
file on viper, and it went through quite fast.
Is it always like this for different versions, and what is the config of
your machine?
Yong.
On Fri, 6 Jul 2007, Ben Clifford wrote:
>
> the xml->kml conversion took long time when I tried to compile nika's
> .swift file.
>
> I can leave it running overnight and see if it ends...
>
> On Fri, 6 Jul 2007, Yong Zhao wrote:
>
> > I don't think the compilation takes that much time. It is the starting
> > time from loading the kml file to dispatching the first job that takes a
> > long time (for 20k jobs).
> >
> > Yong.
> >
> > On Fri, 6 Jul 2007, Mihael Hategan wrote:
> >
> > > On Fri, 2007-07-06 at 16:02 +0000, Ben Clifford wrote:
> > > >
> > > > On Fri, 6 Jul 2007, Mihael Hategan wrote:
> > > >
> > > > > That makes sense. We need to speed up compilation?
> > > >
> > > > I think more important is concentrating on the langauge features necessary
> > > > to have smaller source files.
> > >
> > > Yes, of course. But the compilation time is still ridiculous,
> > > considering that it doesn't do much fancy stuff?
> > >
> > > >
> > > > I'm working with Nika on that at the moment.
> > > >
> > >
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
> >
> >
>
From hategan at mcs.anl.gov Fri Jul 6 11:30:31 2007
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Fri, 06 Jul 2007 11:30:31 -0500
Subject: [Swift-devel] recent karajan changes causing trouble
In-Reply-To:
References:
<1183429417.16404.0.camel@blabla.mcs.anl.gov>