Description
If I have provided 1 day lag in predecessor's then it is converted into 4800 while saving it as XML
Please find the prepared link I have created in MS Project
Predecessor with lag:
Please find the link lag in XML:
How can I find the calculation behind this?
Assuming you are using MS Project's standard calendar, the calculation seems to be the duration in minutes (One 8hr work day = 480 minutes of duration) multiplied by 10 (480 x 10 = 4800).
Related
I am following this answer to calculate number of hot days in a year (temperature exceeding 35degC) from daily tmax data.
I am using tmax from CHELSA from 2000-2016, and I have crop it based on my bounding-box requirement.
Here are the steps I have done (example using 2001 data - 1 month 1 nc file):
Merge monthly data to annual: cdo mergetime chelsa_daily_2001*.nc chelsa_annual_2001.nc
Calculate hot days: cdo gec,308.15 chelsa_annual_2001.nc chelsa_hotdays_2001.nc The Chelsa's temperature is in Kelvin, so threshold for hot days is 308.15
Sum number of days in a year: cdo yearsum chelsa_hotdays_2001.nc chelsa_hotdays_yearsum_2001.nc
And below is the result and unfortunately not what I expected.
Why the number of days is not in integer? Did I missed something in the script?
UPDATE1 (following response from Adrian)
I have installed ncview via homebrew but unfortunately can't open. Got following error:
Note: could not open file /Users/xxx/.ncviewrc for reading
Error: Can't open display:
I try to open the nc output using QGIS, and the result still in float.
UPDATE2
Ok, I managed to check it using ncdump, and here's the first line that contains the value. Bit confuse, because I tried using 1 year data and the total is more than 365. How did it happen?
I strongly suspect panoply is performing some kind of spatial interpolation on the data on import.
Please take a look at the raw field directly using ncdump like this
ncdump chelsa_hotdays_yearsum_2001.nc | less
(I pipe to less so you can stroll down through the data). Or alternatively you can open the file in ncview and move the cursor over the data and you will see the field values displayed in the dialog box.
ncview chelsa_hotdays_yearsum_2001.nc
I am facing a problem when I am assigning a one day task to a resource who works for 9hrs/day but with 25% availability. Following are the steps
Created a calendar with 9hrs as working hours (for all days) as shown below
Assigned availability to "Dummy" Resource as shown below
Created a 1 day task "Dummy" as shown below
Problem is
Work Column must be 2.25 hrs
Calculation: Dummy resource for 9hrs/day at 25% availability = (25/100)*9 hrs = 2.25hrs
but it is showing is 2.13 hrs
How to assign a long duration task (say 1 year) to above resource with different availability (as shown in image above). [Note: There are other resource who work for 8hrs/day with different availibility hence I cannot change MS Project "OPTIONS"]
I have created 3 calendars - CAL_1, CAL_2 and CAL_3 for 3 different locations. Each location has its own non-working days in each quarter. For example 15 weekdays are not working in Mar, Jun, Sept, Dec in CAL_1 every year. 10 weekdays in same manner for CAL_2 every year and so on. Is there any VBA script by which I can automate such work for every year (note: weekends are not included).
I am using max msp and the sql object described here :
https://cycling74.com/2008/09/05/data-collection-building-databases-using-sqlite/
I basically want to record an electrical voltage which I have streaming into max every 20 ms for 24 hours so I can play it back at various different speeds. Any idea how much space this is going to use up ? Id like to do this over 8 channels so 8 channels for 24 hours taking a sample every 20 ms - any tips appreciated.
This depends on the table structure and on the contents of the rows.
With eight integers per row, like in this Python test script:
import sqlite3
db=sqlite3.connect('logger.db')
c=db.cursor()
c.execute('CREATE TABLE log(ch1,ch2,ch3,ch4,ch5,ch6,ch7,ch8)')
for i in xrange(50*60*60*24):
c.execute('INSERT INTO log VALUES(1,2,3,4,5,6,7,8)')
db.commit()
the database ends up at about 100 MB.
I'm facing difficulties to show the time time difference in hours where hours are greater than 24.
Right now I'm using the following in iReport
(new SimpleDateFormat("dd':'HH':'mm':'ss")).format(new Date($V{avgDuration}.longValue()*1000))
where $V{avgDuration} is a variable in jrxml file which is the average time difference between two dates in seconds. Here it shows the 1 day 1 hour but I want it to be 25 hour. What should I do?
I've solved the problem using PeriodFormatterBuilder. But for this, I need to use joda-time library.
In the expression editor of the text box in jrxml file, just wrote the following:
new org.joda.time.format.PeriodFormatterBuilder()
.printZeroAlways()
.minimumPrintedDigits(2)
.appendHours().appendSeparator(":")
.appendMinutes().appendSeparator(":")
.appendSeconds()
.toFormatter()
.print(new org.joda.time.Period(
$V{avgDuration}.longValue()*1000))
I have one number that has something related to the currentdate :
634101448539930000
634101448627430000 (this information was took 9 seconds later than the first one)
I have many codes like this and I need to know what those number means. It's something related to the current time, because the new information has always a bigger number than the older ones.
Please if anybody could help me, thanks
It's a Tick Count.
There are 10,000 ticks in 1 ms. That number is the number of milliseconds that have passed since January 1st, 0001 at midnight.
This particular tick count represents the date/time 2010-05-22 17:07:33 (makes sense, since that's today).
Well, the second number is 87500000 greater than the first, and since they're about 9 seconds apart, I'd guess it was number of 100 nanoseconds since some epoch.
If you divide the number by 1x10^7, you get approximately the number of seconds since 1 Jan 0001 (ignoring the calendar reforms and all that stuff).
Dates and times are generally stored as a single number in computer languages. The number usually represents an offset from a specific data. For example it might be an offset from 1 Jan 1970. Usually you don't deal with these numbers. I suspect that if you look at your APIs you will find a function to convert these numbers into more meaningful representations.
It appears that those numbers represent your system's internal system time with precision down to the decimicrosecond (one ten-millionth of a second), as measured from the date January 1st, 1 A.D.
634101448627430000 - 634101448539930000 = 87500000
87500000 / 10,000,000 = 8.75
And, using Perl's Time::Duration module:
&duration_exact(634101448627430000/10_000_000);
2010 years, 263 days, 17 hours, 7 minutes, and 42 seconds
So from that we know that 63410144862 seconds ago was 2010 years ago, so the timestamp is based at the year 1 A.D.
It could be a variation of Unix Time ( a converter for unix time is available here ).
Unix time is a way of representing a date/time as a number that is easy to store and compare. Your numbers may be a substring of unix time, or may be a format designed by the author. I would examine your ASP.NET code to check how it is used, and you'll find out what it means.