WARNING: This website is obsolete! Please follow this link to get to the new Albert@Home website!

Drupal migration coming up!

Message boards : News : Drupal migration coming up!
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Oliver Behnke
Volunteer moderator
Project administrator
Project developer

Send message
Joined: 4 Sep 07
Posts: 130
Credit: 8,545,955
RAC: 0
Message 112816 - Posted: 31 Mar 2014, 11:34:20 UTC
Last modified: 31 Mar 2014, 11:35:52 UTC

Hi everyone,

After a longer public beta phase we decided that it's about time to migrate albert's web interface to Drupal proper. We're aware that some features we intend to provide for production (on einstein later on) aren't yet fully implemented and we also expect that there will be a few yet unknown bugs. However, albert is our test project after all, so let's get serious about it. The more people are using the new interface, the better we can prepare it for production use. So thanks in advance for your patience and feedback!

We're going to prepare this step over the coming days and will start without further notice.

For you this means that albert might soon be down for maintenance and data migration. The migration, once started, shouldn't take longer than a few days. Should we encounter significant issues or show stoppers we'll have back-out plans at hand and revert to the standard interface again.

See you on the other side...


Cheers,
Oliver
ID: 112816 · Report as offensive     Reply Quote
tjreuter

Send message
Joined: 11 Feb 05
Posts: 25
Credit: 2,084,544
RAC: 0
Message 112824 - Posted: 3 May 2014, 13:57:40 UTC - in response to Message 112816.  

Hello,

Is this project still working?
I don't see any changes yet and I am not getting new work on several PC's with different set-up's.
Thank you for your time.
Greetings from,
TJ.
ID: 112824 · Report as offensive     Reply Quote
mountkidd

Send message
Joined: 30 Jul 13
Posts: 1
Credit: 6,649,331
RAC: 0
Message 112826 - Posted: 7 May 2014, 17:00:53 UTC - in response to Message 112816.  

Hi Oliver,

Can we get an update on the migration? It's been a while...

Gord
ID: 112826 · Report as offensive     Reply Quote
Profile Gibson Praise

Send message
Joined: 10 Jun 13
Posts: 3
Credit: 35,579,146
RAC: 0
Message 112827 - Posted: 9 May 2014, 22:09:02 UTC - in response to Message 112826.  

Can we get an update on the migration? It's been a while...

I've been wondering the same thing, and I'm sure others have. However it is good to remember that:
"Most of the time Albert@Home will have no work to run at all, and when it has, the applications are experimental, might be unstable, unreliable and may even damage your computer. Validation might be unreliable and we may cancel workunits without prior notice." (from the home page of Albert).

This is especially true since Albert is generally only used by Einstein@home to test beta server code. Beta application code is usually tested on Einstein@home. There was a recent post by Bernd (responding to why such testing was not done at Albert) which I include below. It's very informative.

Sorry, but why this is not done at Albert@home?


Albert@Home was originally set up to test server side code, including changes that were necessary to support new applications (e.g. locality scheduling). Historically we were testing Beta App versions on Einstein as "anonymous platform packages" as long as we had only one search (i.e. application). With the introduction of a second search (BRP), maintainig app_info.xml files became a hazzle, so we switched to testing new app versions on Albert. This, however, has its own drawbacks:

- Providing the right amount of "work" of the right type (that belongs to the App version that we want to test) is getting increasingly difficult. We e.g. need to maintain a separate line of code for each workunit generator.

- The computing power and thus throughput on Albert is not very high, so you need to repeatedly reconfigure the system to not waste any on applications that you don't want to test right now.

- When you issue a new series of application versions and generate work for it, validation compares results of these only to that of versions of the same series. A comparison to the result of an established version - which is what we really want - happens only in very rare, accidental cases.

- the variation of different systems attached to Albert is not at all representative for what's running on Einstein.

- due to the low throughput, especially when tasks are assigned with additional constraints (locality scheduling), feedback (i.e. validation) is very slow, slowing down development.

- App version testing is not independent from the server code. Occasionally the need for testing application version prevented us from testing server side changes on Albert, or at least required us to postpone these.

For us these were enough arguments to shift testing of application versions back to Einstein. Server code and new applications will still be tested on Albert, and I think for some time at least BRP app versions, too.

BM


Cheers to all,
G
ID: 112827 · Report as offensive     Reply Quote
Profile Oliver Behnke
Volunteer moderator
Project administrator
Project developer

Send message
Joined: 4 Sep 07
Posts: 130
Credit: 8,545,955
RAC: 0
Message 112829 - Posted: 15 May 2014, 13:37:31 UTC - in response to Message 112827.  

Sorry guys, I completely missed your posts :-/

I was just about to post a small update as we're about to start the migration next week!

Best,
Oliver

ID: 112829 · Report as offensive     Reply Quote

Message boards : News : Drupal migration coming up!



This material is based upon work supported by the National Science Foundation (NSF) under Grant PHY-0555655 and by the Max Planck Gesellschaft (MPG). Any opinions, findings, and conclusions or recommendations expressed in this material are those of the investigators and do not necessarily reflect the views of the NSF or the MPG.

Copyright © 2019 Bruce Allen for the LIGO Scientific Collaboration