Re: [SAGA-RG] SAGA Projects in Google Summer of Code
We should now next week what applciations came in, and shortly after what projects really start. Yes, the window is tight, but any distribution of the call is very welcome :-) Andre. Quoting [Craig Lee] (Mar 31 2008):
To: Andre Merzky <andre@merzky.net>, SAGA RG <saga-rg@ogf.org>, SAGA Impl List <saga-devel@cct.lsu.edu> From: lee@aero.org Subject: Re: [SAGA-RG] SAGA Projects in Google Summer of Code Cc: msc@ogf.org
Fantastic!
Given the very narrow application window (they probably get tons of applications) it is probably too late to do any more publicizing. When do we know if any SAGA projects get started?
--Craig
At 7:32 AM +0100 3/29/08, Andre Merzky wrote:
Forward from Shantenu:
Google have agreed to fund possible SAGA projects via OMII-UK as part of their "Summer of Code" project
http://code.google.com/soc/2008/ http://www.omii.ac.uk/wiki/MPGoogleSAGA
Google will begin accepting student applications on March 24. If you know students who might be interested, please encourage them to submit applications. The application deadline is, unfortunately, already next week.
Shantenu
-- One week of hacking easily saves half an hour of thinking. Henri Bal -- saga-rg mailing list saga-rg@ogf.org http://www.ogf.org/mailman/listinfo/saga-rg
-- One week of hacking easily saves half an hour of thinking. Henri Bal
Hi All, the deadline for student applications has been extended by a week to April 7th. Please encourage your students to take a look at the project ideas proposed around SAGA and formulate their applications. If they submit early then we will be able to give them feedback. cheers, neil
-----Original Message----- From: saga-rg-bounces@ogf.org [mailto:saga-rg-bounces@ogf.org] On Behalf Of Andre Merzky Sent: 31 March 2008 10:29 To: lee@aero.org Cc: msc@ogf.org; SAGA Impl List; SAGA RG; Andre Merzky Subject: Re: [SAGA-RG] SAGA Projects in Google Summer of Code
We should now next week what applciations came in, and shortly after what projects really start. Yes, the window is tight, but any distribution of the call is very welcome :-)
Andre.
To: Andre Merzky <andre@merzky.net>, SAGA RG <saga-rg@ogf.org>, SAGA Impl List <saga-devel@cct.lsu.edu> From: lee@aero.org Subject: Re: [SAGA-RG] SAGA Projects in Google Summer of Code Cc: msc@ogf.org
Fantastic!
Given the very narrow application window (they probably get tons of applications) it is probably too late to do any more publicizing. When do we know if any SAGA projects get started?
--Craig
At 7:32 AM +0100 3/29/08, Andre Merzky wrote:
Forward from Shantenu:
Google have agreed to fund possible SAGA projects via OMII-UK as part of their "Summer of Code" project
http://code.google.com/soc/2008/ http://www.omii.ac.uk/wiki/MPGoogleSAGA
Google will begin accepting student applications on March
Quoting [Craig Lee] (Mar 31 2008): 24. If you
know students who might be interested, please encourage them to submit applications. The application deadline is, unfortunately, already next week.
Shantenu
-- One week of hacking easily saves half an hour of thinking. Henri Bal -- saga-rg mailing list saga-rg@ogf.org http://www.ogf.org/mailman/listinfo/saga-rg
-- One week of hacking easily saves half an hour of thinking. Henri Bal -- saga-rg mailing list saga-rg@ogf.org http://www.ogf.org/mailman/listinfo/saga-rg
-- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
Hi Andre, Havent seen any traffic on the email list for a while, so emailing you directly in case it has broken again ... In the specification for jobs, there are two definitions for job state: /** Metric name, fires on state changes of the job. */ public static final String JOB_STATE = "job.state"; // Optional metrics: /** Metric name, fires as a job changes its state detail. */ public static final String JOB_STATEDETAIL = "job.state_detail"; Now, if something is defined as a metric, does this mean it is also available as an attribute? The definition for metrics states that they are for monitoring changes to the value, however in my case I simply want to get the current value rather than monitoring it. Am I missing something here? Cheers, Malcolm.
Malcolm,
Havent seen any traffic on the email list for a while, so emailing you directly in case it has broken again ...
In the specification for jobs, there are two definitions for job state:
/** Metric name, fires on state changes of the job. */ public static final String JOB_STATE = "job.state"; // Optional metrics: /** Metric name, fires as a job changes its state detail. */ public static final String JOB_STATEDETAIL = "job.state_detail";
Now, if something is defined as a metric, does this mean it is also available as an attribute? The definition for metrics states that they are for monitoring changes to the value, however in my case I simply want to get the current value rather than monitoring it. Am I missing something here?
The metric object exposes the attribute interface. Further, the metric uses a specific attribute to store its value (I think the name of this attribute was "metric.value"). In your example above the job exposes two attributes: job.state and job.state_detail, which are additionally available for monitoring (i.e. fire a metric if something is registered with them). So the answer to your question is, that you simply can ask the job for its attributes to get the current job state, no need to register a callback function here. HTH Regards Hartmut
participants (4)
-
Andre Merzky -
Hartmut Kaiser -
Malcolm Illingworth -
neil p chue hong