[emboss-dev] (no subject)

[jitesh dundas]

Dear Sir,

I hope my previous email gave you a clear idea of my plan on this task.

I will begin working on the code now. I will keep you posted every 2
days with my progress.

Please let me know if you need anthing else from my side.

Regards,
Jitesh Dundas

On 6/10/09, jitesh dundas <jbdundas at gmail.com> wrote:
> Dear Sir,
>
> Thank you for your reply. PLEASE FIND MY COMMENTS IN BLOCK LETTERS BELOW.
>
> On 6/9/09, Peter Rice <pmr at ebi.ac.uk> wrote:
>> Dear Jitesh,
>>
>>> I need to know the priority on which any script/ application in EMBOSS
>>> is executed.
>>
>> Currently, all EMBOSS applications simply execute.
>>
>> When they terminate, if EMBOSS_LOGFILE is defined they can write a
>> single record the the logfile.
>>
>> However, we can extend this is that is what you are suggesting.
>>
>> All EMBOSS (and EMBASSY) applications start with a call to ajAcdInit
>> (often via embInitP or ajGraphInit)
>>
>> All EMBOSS applications end with a call to ajExit on success. Failed
>> applications should call ajExitBad or ajExitAbort ... unless they crash
>> with a segmentation fault or are otherwise terminated.
>>
>> So we have places to put in additional monitoring code.
>
> I NEED THE CENTRAL LOCATION FROM WHERE THIS MONITORING SCRIPT CAN BE
> ACCESSED. AN INTERFACE THAT WILL BE AT THE HEART OF EMBOSS. THIS WILL
> BE A COMMON SCRIPT AND THUS, IT MUST HAVE ACCESS TO ALL  SCRIPTS.
>
>>> If applications in Emboss are to be executed, they need to be assigned
>>> a priority or an impact , besides the following:-
>>>
>>> 1) A master database or a table that stores list of applications
>>> running. These will be updated by a scheduled script running
>>> continuously in the background.
>>
>> This script, could, for example, check the list of known running
>> applications and remove any that appear to have crashed.
>>
>>> 2) the front-end GUI needs to showing a chart of applications running
>>> and parameters like progress, time consumed etc.
>>>
>>> Measuring progress needs some breakpoints. Their status will be
>>> pending,WIP or completed.
>>
>> We have no breakpoints in EMBOSS at present. Can you give examples of
>> what you have in mind?
>
> FOR E.G.) there are 5 stages/applications running in parallel. EACH
> STAGE WILL BE DIVIDED INTO PARTS,WHERE  EACH PART'S END-POINT ACTING
> AS  A COMPLETION SUB_TARGET.
>
> THE ENTRY IN DATABASE TABLE WILL HAVE A  PROCESS,SUB-PROCESS,STATUS
> FIELDS. DETAILS OF EACH FIELD ARE ENTERED HERE.
> tHE SCRIPT OR THE INTERFACE WILL RUN AND MONITOR THE EXECUTION
> PROGRESS OF EACH STAGE. REGULARLY, IT WILL UPDATE THE DATABASE TABLE.
>
>>> I will send further details in 1-2 days. Meanwhile, i request your
>>> feedback.
>>
>> Hope this helps.
>>
>> Peter Rice
>>
>
> PLEASE LET ME KNOW IF YOU NEED ANYTHING ELSE FROM MY SIDE.
>
> --
> Thanks & Regards,
> Jitesh Dundas
>
> Scientist, Edencore Technologies(www.edencore.net)
> Web Developer, JR Technologies, India
>
> Phone:- +91-9860925706
>
> http://jiteshbdundas.blogspot.com
>
> "NO IDEA IS STUPID,EITHER IT IS TOO GOOD TO BE TRUE OR IT IS WAY AHEAD
> OF ITS FUTURE "- GEORGE BERNARD SHAW.
>


-- 
Thanks & Regards,
Jitesh Dundas

Scientist, Edencore Technologies(www.edencore.net)
Web Developer, JR Technologies, India

Phone:- +91-9860925706

http://jiteshbdundas.blogspot.com

"NO IDEA IS STUPID,EITHER IT IS TOO GOOD TO BE TRUE OR IT IS WAY AHEAD
OF ITS FUTURE "- GEORGE BERNARD SHAW.