rpi_logo
Posts by hans_lion
Posts by hans_lion
log in
1) Message boards : Number crunching : Problem with new W/Us (Message 3571)
Posted 29 May 2008 by Profile hans_lion
Got a task from this WU.
name: gs_3737082_1211956623_998318_3
WU name: gs_3737082_1211956623_998318
app version num: 122
checkpoint CPU time: 0.000000
current CPU time: 1258.242634
fraction done: 0.000000

According to the posts above it's funny that
the reverse of the fraction-done-value gives ...
NaN :-)

EDIT: when I'd reported my aborted task,
the next one was created immediately afterwards.

This may be overcome, as seen on SAH beta, by setting max#oftotaltasks to zero in the concerned WU's.

EDIT2: Anonymous got it onto it's host.
2) Message boards : Number crunching : More Work !!! Please :) (Message 2305)
Posted 17 Mar 2008 by Profile hans_lion

Very pretty!
Since the SuperNova made by Al there seems to be
1. a very stable server :-)
2. serving a countdown for new work:
Results in progress 6,472 [As of 17 Mar 2008 11:48:22 UTC]
Results in progress 6,408 [As of 17 Mar 2008 12:02:15 UTC]

You may agree: it counts too slowly!!!
3) Message boards : Number crunching : More Work !!! Please :) (Message 2257)
Posted 14 Mar 2008 by Profile hans_lion

the reason we can't have more than 20 WUs at a time (and even this is too many) has been discussed on here many times. it's even in the known issues section. what we're doing is dynamically updating a genetic search based on the results you guys return. if we feed out more than 20 workunits (even this is too many) by the time you finish crunching them, the population has moved so far away from where those points were generated that the work you've done on them is basically useless. ideally i'd really like to have the number somewhere around 5-10.

when we update the server code, you should be able to download new workunits as soon as you finish with your previous ones. if you're just complaining about wanting more WUs out there in the case when the server crashes... i don't think theres anything we can do about that as the workunits need to be dynamically generated as new ones come in.

that being said, we definitely are trying to increase the time per workunit. the model will be updated, and we'll be doing it across multiple streams of stars - you just need to be patient with us here. this is science in progress and Nate is working on how exactly to do that. also, i'm working on incorporating doing a line search into a workunit (which should increase the computation time by a factor of 10-50) or more) -- but that's maybe a week or two away because that'll take a bit of bug fixing. i'm hoping to have that in the next version of the application.


I've set "Connect about every 0.01 days" and "Additional work buffer 0.05 days" in order to get just few WU's at a time.

Hans
4) Message boards : Number crunching : More Work !!! Please :) (Message 2256)
Posted 14 Mar 2008 by Profile hans_lion
First WUs are arrivig on my comps@home! YAY! :-)
Although my lappy is still ignored by now. *grin*

PS. I guess all the boxes attached to Milkyway are so busy fetching work that the WUs are gone before the server status can show them as results to send. *biiiig grin*

Travis wrote:

the reason we can't have more than 20 WUs at a time (and even this is too many) has been discussed on here many times. it's even in the known issues section. what we're doing is dynamically updating a genetic search based on the results you guys return. if we feed out more than 20 workunits (even this is too many) by the time you finish crunching them, the population has moved so far away from where those points were generated that the work you've done on them is basically useless. ideally i'd really like to have the number somewhere around 5-10.

when we update the server code, you should be able to download new workunits as soon as you finish with your previous ones. if you're just complaining about wanting more WUs out there in the case when the server crashes... i don't think theres anything we can do about that as the workunits need to be dynamically generated as new ones come in.

that being said, we definitely are trying to increase the time per workunit. the model will be updated, and we'll be doing it across multiple streams of stars - you just need to be patient with us here. this is science in progress and Nate is working on how exactly to do that. also, i'm working on incorporating doing a line search into a workunit (which should increase the computation time by a factor of 10-50) or more) -- but that's maybe a week or two away because that'll take a bit of bug fixing. i'm hoping to have that in the next version of the application.


This means, stars are evolving by talking from WU to WU, as, for instance, Cori does.
So, Cori evolves to be a star <3
One of the miracles of MilkyWay :-)
5) Message boards : Number crunching : Assimilator looks to be down again (Message 2194)
Posted 12 Mar 2008 by Profile hans_lion
now we are up to 27,751 and no new work.


I tried to kill the process and restart it myself. Guess its not letting me though. I've submitted a report to labstaff.


milkyway przybd $ kill 15963
-bash: kill: (15963) - Operation not permitted
milkyway przybd $ sudo kill 15963
Password for przybd@LAB.CS.RPI.EDU:
Sorry, user przybd is not allowed to execute '/bin/kill 15963' as root on milkyway.cs.rpi.edu.



Looks like milkyway wanting you directly at console.
You know TRON :?)

Another try:
/bin/su
(roots password)
/bin/kill 15963
/bin/kill -9 15963 (or /bin/kill -KILL 15963)
(complaining about proc not found shows success of former /bin/kill)
exit (from root shell)

Good luck,
Hans




Main page · Your account · Message boards


Copyright © 2019 AstroInformatics Group