If you’ll enter the duration or units value in hours, it should be ok. As I wrote, I only found those rounding errors only in the calculation between display: in days and save: in hours with decimals. No need to change user preferences if you want to enter a value in hours. Just type the value in hours followed by "h" - or your abbreviation for hours, if you modified it.
In brief, the error is due to time conversion from hour to day. If I change to dislay in hour and input value 4040 hours (=505 days) and then display in day for report purpose, Primavera will display duration in day correctly, is it right?
Im little doubt at this solution. Because I didnt change the value in "Time Period" in Admin Preference and in User Preference. There is no difference between them.
Regards
Member for
18 years 9 months
Member for18 years9 months
Submitted by Dieter Wambach on Sun, 2009-06-07 05:29
I agree to Vladimir. When I checked for the size of different projects, I found that big usage (10 to 15 per activity, for whatever reason) of coding has much mor influence on memory consumption.
Another factor are notebook items and relations to documents. It wasnt that much the size by number of activities.
Regards
Dieter
Member for
24 years 8 months
Member for24 years9 months
Submitted by Vladimir Liberzon on Fri, 2009-06-05 19:22
As bizarre as it sounds, P6 calculates the CPM in minute increments (even 500 day schedules.) Now you can see why Primavera lists 2 GB of memory as a minimum requirement for your computer.
Spider Project calculates schedules in seconds but does not require any special memory. So this is not the reason why P6 needs 2 GB.
Best Regards,
Vladimir
Member for
18 years 9 months
Member for18 years9 months
Submitted by Dieter Wambach on Fri, 2009-06-05 12:36
I don’t feel like picked. I didn’t mention the units less than an hour. How many digits depends on the settings of the database (in Oracle).
Ronald, I’m sure you are much more experienced than me. I’m a user (since 1994 P3 and 2001 P3e)
In the past I stumbled over the same as Khuong Do and felt unsafe of course. So I tested. Now I’m quite confident in the internal calculation. When I need exact results I let units and durations be displayed in hours with decimals and the dates with minutes.
If you have a look into the database, those fields are defined numeric (17,6) for the MS SQL-server - as far as I know, even more in Oracle.
I’ll have no chance to join the AACE meeting, I hope you’ll show your paper on your home page. It would be great.
Best regards
Dieter
Member for
22 years 10 months
Member for22 years10 months
Submitted by Ronald Winter on Fri, 2009-06-05 12:05
I hope that you do not think that I am picking on you. I suspect that you know more about P6 than the current Primavera Development Team. While you are correct in quoting Primavera’s technical manual in stating that P6 calculates the CPM in hours, this clearly is not the case.
Holidays are entered in half hour increments. There would be no reason to do this if the CPM were calculated in hours. Likewise, working day length can be defined in fractions of an hour to (at least) two decimal paces. Durations in the database are stored in hours, but decimal hours accurate down to the microsecond.
I will be delivering a technical paper at the AACEi Annual Conference in July of this year that shows P6 calculating a test schedule down to the even minute. As bizarre as it sounds, P6 calculates the CPM in minute increments (even 500 day schedules.) Now you can see why Primavera lists 2 GB of memory as a minimum requirement for your computer.
Member for
18 years 9 months
Member for18 years9 months
Submitted by Dieter Wambach on Fri, 2009-06-05 11:41
You are right for my calculation; its 14 minutes, not less than one - sorry Khuong Do.
But as the internal calculation is in hours, the overall duration will be ok. For my experience this error just happens in the calculation of the displayed duration. In the past I stumbled over this item as well and checked several times. Result: the calculation in hours was ok. Therefore my suggestion: for an exact check, display durations in hours.
Regards
Dieter
Member for
22 years 10 months
Member for22 years10 months
Submitted by Ronald Winter on Fri, 2009-06-05 09:53
Khuong is working in days. 0.01 days is equal to 14.4 minutes; roughly a quarter of an hour. Due to rounding issues, the real value could be 21 minutes and still display 0.01. I stand with Khuong on this; a $5,000 software package should not be generating one-third of an hour errors. As you pointed out, 500-day schedules consisting of tens of thousands of activities all off by a third of an hour (or more) does not give one a real sense of confidence in the accumulated sum.
Member for
18 years 9 months
Member for18 years9 months
Submitted by Dieter Wambach on Fri, 2009-06-05 09:16
Internally P6 calculates in hours, just to display it calculates hours into days, weeks - whatever you choose as unit. Rounding issues during this calculation may lead to this result. If you’ll need exact figures, you’ll better use hours.
0.01 is less than one minute. Which controlling actions you’ll take to recover? For an activity duration of 500 days it might be a consideration to ignore the decimals.
Member for
1 year 10 monthshello all i have issue
hello all
i have issue ...the original duration for project is less that what should be
actually it should be 260 day but its only 212
i checked calender and all solution that mentiond before
what should i do [[wysiwyg_imageupload:8563:]]
Member for
1 year 10 monthswysiwyg_imageupload::hello
[[wysiwyg_imageupload::]]
hello all
i have issue ...the original duration for project is less that what should be
actually it should be 270 day but its only 212
i checked calender and all solution that mentiond before
what should i do[[wysiwyg_imageupload:8562:]]
Member for
1 year 10 monthswysiwyg_imageupload::hello
[[wysiwyg_imageupload::]]
hello all
i have issue ...the original duration for project is less that what should be
actually it should be 270 day but its only 212
i checked calender and all solution that mentiond before
what should i do[[wysiwyg_imageupload:8562:]]
Member for
18 years 9 monthsRE: Incorrect duration
Khuong Do
If you’ll enter the duration or units value in hours, it should be ok. As I wrote, I only found those rounding errors only in the calculation between display: in days and save: in hours with decimals. No need to change user preferences if you want to enter a value in hours. Just type the value in hours followed by "h" - or your abbreviation for hours, if you modified it.
Regards
Dieter
Member for
16 years 5 monthsRE: Incorrect duration
Hi Dieter and Ronald.
Thanks so much for your help.
In brief, the error is due to time conversion from hour to day. If I change to dislay in hour and input value 4040 hours (=505 days) and then display in day for report purpose, Primavera will display duration in day correctly, is it right?
Im little doubt at this solution. Because I didnt change the value in "Time Period" in Admin Preference and in User Preference. There is no difference between them.
Regards
Member for
18 years 9 monthsRE: Incorrect duration
Ronald, Vladimir
I agree to Vladimir. When I checked for the size of different projects, I found that big usage (10 to 15 per activity, for whatever reason) of coding has much mor influence on memory consumption.
Another factor are notebook items and relations to documents. It wasnt that much the size by number of activities.
Regards
Dieter
Member for
24 years 8 monthsRE: Incorrect duration
Ronald,
you wrote:
As bizarre as it sounds, P6 calculates the CPM in minute increments (even 500 day schedules.) Now you can see why Primavera lists 2 GB of memory as a minimum requirement for your computer.
Spider Project calculates schedules in seconds but does not require any special memory. So this is not the reason why P6 needs 2 GB.
Best Regards,
Vladimir
Member for
18 years 9 monthsRE: Incorrect duration
Ronald
I don’t feel like picked. I didn’t mention the units less than an hour. How many digits depends on the settings of the database (in Oracle).
Ronald, I’m sure you are much more experienced than me. I’m a user (since 1994 P3 and 2001 P3e)
In the past I stumbled over the same as Khuong Do and felt unsafe of course. So I tested. Now I’m quite confident in the internal calculation. When I need exact results I let units and durations be displayed in hours with decimals and the dates with minutes.
If you have a look into the database, those fields are defined numeric (17,6) for the MS SQL-server - as far as I know, even more in Oracle.
I’ll have no chance to join the AACE meeting, I hope you’ll show your paper on your home page. It would be great.
Best regards
Dieter
Member for
22 years 10 monthsRE: Incorrect duration
Dieter,
I hope that you do not think that I am picking on you. I suspect that you know more about P6 than the current Primavera Development Team. While you are correct in quoting Primavera’s technical manual in stating that P6 calculates the CPM in hours, this clearly is not the case.
Holidays are entered in half hour increments. There would be no reason to do this if the CPM were calculated in hours. Likewise, working day length can be defined in fractions of an hour to (at least) two decimal paces. Durations in the database are stored in hours, but decimal hours accurate down to the microsecond.
I will be delivering a technical paper at the AACEi Annual Conference in July of this year that shows P6 calculating a test schedule down to the even minute. As bizarre as it sounds, P6 calculates the CPM in minute increments (even 500 day schedules.) Now you can see why Primavera lists 2 GB of memory as a minimum requirement for your computer.
Member for
18 years 9 monthsRE: Incorrect duration
Ronald
You are right for my calculation; its 14 minutes, not less than one - sorry Khuong Do.
But as the internal calculation is in hours, the overall duration will be ok. For my experience this error just happens in the calculation of the displayed duration. In the past I stumbled over this item as well and checked several times. Result: the calculation in hours was ok. Therefore my suggestion: for an exact check, display durations in hours.
Regards
Dieter
Member for
22 years 10 monthsRE: Incorrect duration
Dieter,
Khuong is working in days. 0.01 days is equal to 14.4 minutes; roughly a quarter of an hour. Due to rounding issues, the real value could be 21 minutes and still display 0.01. I stand with Khuong on this; a $5,000 software package should not be generating one-third of an hour errors. As you pointed out, 500-day schedules consisting of tens of thousands of activities all off by a third of an hour (or more) does not give one a real sense of confidence in the accumulated sum.
Member for
18 years 9 monthsRE: Incorrect duration
Khuong Do
Internally P6 calculates in hours, just to display it calculates hours into days, weeks - whatever you choose as unit. Rounding issues during this calculation may lead to this result. If you’ll need exact figures, you’ll better use hours.
0.01 is less than one minute. Which controlling actions you’ll take to recover? For an activity duration of 500 days it might be a consideration to ignore the decimals.
Regards
Dieter