[OpenMOLE-devs] Web front-end for openmole.
romain.reuillon at iscpif.fr
Fri Jan 11 17:49:31 CET 2013
I think it is premature optimisation. I will be more state to store and
manage on the server side, making it less robust. As the workflow XML
are not that big and an execution is very long compared to the time to
upload a workflow. From my point of view, this optimisation doesn't
worth the complexity it implies.
On 11/01/2013 17:43, Mark Hammons wrote:
> I was thinking that the mole submission form could have a way to save
> commonly used workflow batches as a kind of template, so the scientist
> can just input the new data he wants processed by the workflow each
> time. In the Bioemergence case the well known WFs could be added once
> and then used many times by Biomergence scientists.
> On Fri, Jan 11, 2013 at 5:40 PM, Mathieu Leclaire
> <mathieu.leclaire at iscpif.fr <mailto:mathieu.leclaire at iscpif.fr>> wrote:
> It sounds good. It looks like the schema we drew with Manu the other
> day: a server application generates OpenMOLE executions according to
> a xml serialized workflow and a set of parameters. In the case of
> Bioemergence, the serialized WF are well known and should be
> available for the scientist through a list (it does not need te load
> a WF or it can do that optionaly). Each execution is mapped to an
> ID, which permits to ask the server for the execution states.
> Congrats Mark, it's 5.30pm and you're still awake :) !
> Le 11/01/2013 17:27, Mark Hammons a écrit :
>> I was discussing this with Matthieu the other day, but I have a
>> little demo application for play built, and it looks very simple
>> and easy to use/understand, so we're thinking the play framework
>> would be appropriate for an openmole GUI.
>> I have a couple things I need clarified though. We can have the
>> web interface be a part of the openmole process, so that when you
>> start openmole, the play server is started and you can view the
>> progress of your work, but I think that is not a good idea unless
>> the openmole process becomes a server in of itself.
>> I am thinking the webserver should create and monitor open mole
>> processes. I was thinking there would be a web form where the
>> scientist can fill in the data and information necessary, select
>> a serialized mole xml from his computer, and tell the server to
>> run the mole. Then the server would initiate the openmole program
>> with the parameters, give the scientist a process ID, and then the
>> scientist could view and control the progress of the mole from
>> another webpage. Does this sound good to you guys?
>> Mark Edgar Hammons II - OU Student | Contributor to OpenMOLE
>> Cell - 1 (405) 928 8206 <tel:1%20%28405%29%20928%208206>
>> Email - markehammons at gmail.com <mailto:markehammons at gmail.com>
>> OpenMOLE-devs mailing list
>> OpenMOLE-devs at iscpif.fr <mailto:OpenMOLE-devs at iscpif.fr>
> OpenMOLE-devs mailing list
> OpenMOLE-devs at iscpif.fr <mailto:OpenMOLE-devs at iscpif.fr>
> Mark Edgar Hammons II - OU Student | Contributor to OpenMOLE
> Cell - 1 (405) 928 8206
> Email - markehammons at gmail.com <mailto:markehammons at gmail.com>
> OpenMOLE-devs mailing list
> OpenMOLE-devs at iscpif.fr
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3892 bytes
Desc: S/MIME Cryptographic Signature
More information about the OpenMOLE-devs