JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DAWN Archives


DAWN Archives

DAWN Archives


DAWN@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DAWN Home

DAWN Home

DAWN  December 2013

DAWN December 2013

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Workflow moved to use Passerelle actor v5

From:

Gero Flucke <[log in to unmask]>

Reply-To:

Main mail list for the dawn collaboration <[log in to unmask]>

Date:

Wed, 4 Dec 2013 09:38:47 +0100

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (68 lines)

On Tue, 3 Dec 2013, Olof SVENSSON wrote:

> I have committed patches that make DAWN workflow implementation use the 
> Passerelle actor v5. These changes are necessary in order to take advantage 
> of the latest Passerelle developments, e.g. the event director, connection to 
> a database for task-based tracing etc.
>
> I have worked on these patches for a couple of weeks and they are thoroughly 
> tested. All headless tests pass and I have also tested to run our beamline 
> workflows. However, it's likely that you will have some error messages when 
> trying to start existing workflows with the new DAWN version:
>
> * The expression mode parameter has now been completely removed. If an
>   existing workflow .moml file contains this parameter the following
>   error will be displayed:
>
> All you have to do is to press ok and then save the workflow. The expression 
> mode will then be removed from the moml file so the next time you open this 
> workflow there will be no error message. Matt and Baha are proposing to make 
> this cleaning of the moml file automatically.

Hi all,
there is one disadvantage with anautomatic cleaning:
At least I am often switching back and forth between DAWN versions, e.g. 
between my development version and the current release, working in the 
same workspace. If I now would switch forward and backward again,  I guess 
that teh old version would not be able to understand correctly the .moml 
file. If that is true, I'd suggest not to do the cleaning fully automatic, 
but to ask for user confirmation, indicating the consequences.

> * If you would like to use the new event director you must delete any
>   existing "WorkflowConfiguration.launch" file in your project,
>   otherwise the event director class cannot be found by the workflow
>   engine.

Also not very nice - can that be done semi-automatic (i.e. with 
confirmation) as well? Are there any problems when switching back to an 
older release then?
But if everything else works without this removing sucha file, it might 
be sufficient to add this caveat to a documentastion of the new 
director.

Cheers

 	Gero


> Please let me know if you see any other problems with this new version of the 
> DAWN workflow implementation.
>
> Regards,
>
> Olof
>
>
>

--
-----------------------------------------------------------------------
Gero Flucke
Group 'Experiment Control' (FS-EC)
   * Scientific Software
DESY
Notkestr. 85
22607 Hamburg
Germany
Tel: +49 (0)40 8998 1985

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

September 2023
July 2023
December 2022
April 2022
March 2022
November 2021
November 2019
March 2019
June 2018
May 2018
December 2016
November 2016
October 2016
September 2016
July 2016
June 2016
March 2016
January 2016
September 2015
July 2015
April 2015
March 2015
December 2014
October 2014
September 2014
July 2014
May 2014
April 2014
February 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
January 2012
March 2011
February 2011


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager