I'd like to see work unit deadlines assigned with a constant processing elapsed time rather than elapsed time based on the CPU time estimates. This would resolve a problem I will have this summer when I can't tell how long it will be when I can't attach my notebook to the Internet due to my going on a river cruise in Europe for almost three weeks.

I currently get work units that take as much as eight hours of CPU time with a deadline about 21 days in the future. Then I get a unit with an estimate of 90 minutes and a deadline three days in the future. As a result I can't depend from day to day when I must be able to connect. I do not intend to schedule my vacation time looking for some place with wi-fi. As a result, I will have to drain my queue before I go instead of (possibly) providing processing time for the better part of three weeks.

Making this change would make special processing due to deadline considerations a thing of the past.

If there is currently any way to manipulate the preferences to accomplish this, I haven't found it.

Thanks for any assistance anyone can give.

Jim Allen

You get what you get. There are some other projects that would work for this, one would be CPDN, which has units 1 year out, and take a couple of months, to ... depending on the speed of the machine. This way your machine can be busy the whole time on something.

---

My movie https://vimeo.com/manage/videos/502242

I'd like to see work unit deadlines assigned with a constant processing elapsed time rather than elapsed time based on the CPU time estimates. This would resolve a problem I will have this summer when I can't tell how long it will be when I can't attach my notebook to the Internet due to my going on a river cruise in Europe for almost three weeks.

I currently get work units that take as much as eight hours of CPU time with a deadline about 21 days in the future. Then I get a unit with an estimate of 90 minutes and a deadline three days in the future. As a result I can't depend from day to day when I must be able to connect. I do not intend to schedule my vacation time looking for some place with wi-fi. As a result, I will have to drain my queue before I go instead of (possibly) providing processing time for the better part of three weeks.

Making this change would make special processing due to deadline considerations a thing of the past.

If there is currently any way to manipulate the preferences to accomplish this, I haven't found it.

Thanks for any assistance anyone can give.

Jim Allen

No, But we are working on something.

If the server refuses to send work that has a shorter deadline the the connect every X setting, then you could set that to be the time that you are going to be gone on vacation + a couple of days a couple of days before you leave. Then the only work that would be downloaded would have deadlines more than that amount of time in the future, and the current work would have a couple of days to be finished. Make one last connection before you step out of the house to report whatever you can.

Unfortunately, I am not certain that any projects will have this code by that time. Part of the responsibility has to be at the server.

---

BOINC WIKI

I'd like to see work unit deadlines assigned with a constant processing elapsed time rather than elapsed time based on the CPU time estimates. This would resolve a problem I will have this summer when I can't tell how long it will be when I can't attach my notebook to the Internet due to my going on a river cruise in Europe for almost three weeks.

I currently get work units that take as much as eight hours of CPU time with a deadline about 21 days in the future. Then I get a unit with an estimate of 90 minutes and a deadline three days in the future. As a result I can't depend from day to day when I must be able to connect. I do not intend to schedule my vacation time looking for some place with wi-fi. As a result, I will have to drain my queue before I go instead of (possibly) providing processing time for the better part of three weeks.

Making this change would make special processing due to deadline considerations a thing of the past.

If there is currently any way to manipulate the preferences to accomplish this, I haven't found it.

Thanks for any assistance anyone can give.

Jim Allen

No, But we are working on something.

If the server refuses to send work that has a shorter deadline the the connect every X setting, then you could set that to be the time that you are going to be gone on vacation + a couple of days a couple of days before you leave. Then the only work that would be downloaded would have deadlines more than that amount of time in the future, and the current work would have a couple of days to be finished. Make one last connection before you step out of the house to report whatever you can.

Unfortunately, I am not certain that any projects will have this code by that time. Part of the responsibility has to be at the server.

Thanks for the info, John. I'm not necessarily looking to download more work before I leave home. Extending the number of days between connects would do that with the current (5.8.16) code. I also understand the need for deadlines. I might get killed in a plane crash in this case. But I will leave very early 7/18/2007 and return 8/6, so the current code won't help if I don't know for sure that I can connect without building my whole trip around searches for places where I can connect. I guess I will just have to see what happens and download in the middle of the trip if it seems the thing to do.

Jim

I'd like to see work unit deadlines assigned with a constant processing elapsed time rather than elapsed time based on the CPU time estimates. This would resolve a problem I will have this summer when I can't tell how long it will be when I can't attach my notebook to the Internet due to my going on a river cruise in Europe for almost three weeks.

I currently get work units that take as much as eight hours of CPU time with a deadline about 21 days in the future. Then I get a unit with an estimate of 90 minutes and a deadline three days in the future. As a result I can't depend from day to day when I must be able to connect. I do not intend to schedule my vacation time looking for some place with wi-fi. As a result, I will have to drain my queue before I go instead of (possibly) providing processing time for the better part of three weeks.

Making this change would make special processing due to deadline considerations a thing of the past.

If there is currently any way to manipulate the preferences to accomplish this, I haven't found it.

Thanks for any assistance anyone can give.

Jim Allen

No, But we are working on something.

If the server refuses to send work that has a shorter deadline the the connect every X setting, then you could set that to be the time that you are going to be gone on vacation + a couple of days a couple of days before you leave. Then the only work that would be downloaded would have deadlines more than that amount of time in the future, and the current work would have a couple of days to be finished. Make one last connection before you step out of the house to report whatever you can.

Unfortunately, I am not certain that any projects will have this code by that time. Part of the responsibility has to be at the server.

Thanks for the info, John. I'm not necessarily looking to download more work before I leave home. Extending the number of days between connects would do that with the current (5.8.16) code. I also understand the need for deadlines. I might get killed in a plane crash in this case. But I will leave very early 7/18/2007 and return 8/6, so the current code won't help if I don't know for sure that I can connect without building my whole trip around searches for places where I can connect. I guess I will just have to see what happens and download in the middle of the trip if it seems the thing to do.

Jim

Oh. The computer is going with you. Many hotels now have wireless LAN available (I don't know your itinerary).

---

BOINC WIKI

I'd like to see work unit deadlines assigned with a constant processing elapsed time rather than elapsed time based on the CPU time estimates. This would resolve a problem I will have this summer when I can't tell how long it will be when I can't attach my notebook to the Internet due to my going on a river cruise in Europe for almost three weeks.

I currently get work units that take as much as eight hours of CPU time with a deadline about 21 days in the future. Then I get a unit with an estimate of 90 minutes and a deadline three days in the future. As a result I can't depend from day to day when I must be able to connect. I do not intend to schedule my vacation time looking for some place with wi-fi. As a result, I will have to drain my queue before I go instead of (possibly) providing processing time for the better part of three weeks.

Making this change would make special processing due to deadline considerations a thing of the past.

If there is currently any way to manipulate the preferences to accomplish this, I haven't found it.

Thanks for any assistance anyone can give.

Jim Allen

No, But we are working on something.

If the server refuses to send work that has a shorter deadline the the connect every X setting, then you could set that to be the time that you are going to be gone on vacation + a couple of days a couple of days before you leave. Then the only work that would be downloaded would have deadlines more than that amount of time in the future, and the current work would have a couple of days to be finished. Make one last connection before you step out of the house to report whatever you can.

Unfortunately, I am not certain that any projects will have this code by that time. Part of the responsibility has to be at the server.

Thanks for the info, John. I'm not necessarily looking to download more work before I leave home. Extending the number of days between connects would do that with the current (5.8.16) code. I also understand the need for deadlines. I might get killed in a plane crash in this case. But I will leave very early 7/18/2007 and return 8/6, so the current code won't help if I don't know for sure that I can connect without building my whole trip around searches for places where I can connect. I guess I will just have to see what happens and download in the middle of the trip if it seems the thing to do.

Jim

Oh. The computer is going with you. Many hotels now have wireless LAN available (I don't know your itinerary).

I will be spending a couple of nights in Budapest. Hotel arrangements are dictated by the travel company. The hotel website doesn't say whether there is an Internet connection available anywhere in the hotel. Then I will spend about 15 days on a river boat going up the Danube and down the Main and the Rhine, making stops numerous places between Budapest and Amsterdam. The cruise literature says there are no Internet facilities aboard, but the crew can tell me where to find Internet cafes. There will be a couple of nights in Amsterdam, but at that point I will be almost home. It's the unpredictability of the deadlines coupled to the uncertainty about connection times that makes this a difficult situation. I will be in totally unfamiliar territory. If I could set a deadline of 21 or 22 days and take five or seven days of work with me I might be able to do the project some good. However, I want you to know I appreciate your sharing your insight.

Jim

I'd like to see work unit deadlines assigned with a constant processing elapsed time rather than elapsed time based on the CPU time estimates. This would resolve a problem I will have this summer when I can't tell how long it will be when I can't attach my notebook to the Internet due to my going on a river cruise in Europe for almost three weeks.

I currently get work units that take as much as eight hours of CPU time with a deadline about 21 days in the future. Then I get a unit with an estimate of 90 minutes and a deadline three days in the future. As a result I can't depend from day to day when I must be able to connect. I do not intend to schedule my vacation time looking for some place with wi-fi. As a result, I will have to drain my queue before I go instead of (possibly) providing processing time for the better part of three weeks.

Making this change would make special processing due to deadline considerations a thing of the past.

If there is currently any way to manipulate the preferences to accomplish this, I haven't found it.

Thanks for any assistance anyone can give.

Jim Allen

No, But we are working on something.

If the server refuses to send work that has a shorter deadline the the connect every X setting, then you could set that to be the time that you are going to be gone on vacation + a couple of days a couple of days before you leave. Then the only work that would be downloaded would have deadlines more than that amount of time in the future, and the current work would have a couple of days to be finished. Make one last connection before you step out of the house to report whatever you can.

Unfortunately, I am not certain that any projects will have this code by that time. Part of the responsibility has to be at the server.

Thanks for the info, John. I'm not necessarily looking to download more work before I leave home. Extending the number of days between connects would do that with the current (5.8.16) code. I also understand the need for deadlines. I might get killed in a plane crash in this case. But I will leave very early 7/18/2007 and return 8/6, so the current code won't help if I don't know for sure that I can connect without building my whole trip around searches for places where I can connect. I guess I will just have to see what happens and download in the middle of the trip if it seems the thing to do.

Jim

Oh. The computer is going with you. Many hotels now have wireless LAN available (I don't know your itinerary).

I will be spending a couple of nights in Budapest. Hotel arrangements are dictated by the travel company. The hotel website doesn't say whether there is an Internet connection available anywhere in the hotel. Then I will spend about 15 days on a river boat going up the Danube and down the Main and the Rhine, making stops numerous places between Budapest and Amsterdam. The cruise literature says there are no Internet facilities aboard, but the crew can tell me where to find Internet cafes. There will be a couple of nights in Amsterdam, but at that point I will be almost home. It's the unpredictability of the deadlines coupled to the uncertainty about connection times that makes this a difficult situation. I will be in totally unfamiliar territory. If I could set a deadline of 21 or 22 days and take five or seven days of work with me I might be able to do the project some good. However, I want you to know I appreciate your sharing your insight.

Jim

The best that you can do might be to attach to CPDN and do a WU for them. Or you can wing it with trying to find internet cafes.

---

BOINC WIKI