search for: unitless

...ny parameters don't require the dummy unit arg, ie writing: method foo = ... is fine. The reason you might need the unit arg is if you need to create a closure from the method without calling it, for example if you need to use the method in a callback. In lablgtk2 the convention is to use unitless methods if either: the method shouldn't be used as a callback; or: (conceptually) the method doesn't change the object's internal state. Let's do that here. --- v2v/convert_linux.ml | 2 +- v2v/linux_bootloaders.ml | 14 ++++++-------- v2v/linux_bootloaders.mli | 2 +- 3 f...

...ues that want a free build of the model with the same type of I/O. The Matlab model reads a text file with the initial parameters specified as: C:\Data\Carluc\Rport>more Params.R # Number of years to simulate nYears = 50; # Initial year for graphing purposes year0 = 1970; # NPP/GPP ratio (cpp0 unitless) fnr = 0.30; # Quantum efficency qe = 0.040; That is, there are four input variables (for this run - there can be many more) written in a way that R can understand them. In R, I can have the model source the parameter text file easily enough and have the objects in the workspace. The model functi...

..._east',lons) lat <- dim.def.ncdf('lat','degrees_north',lats) times <- 1:nt tdim <- dim.def.ncdf('time','days since 1980-01-01', times, unlim=TRUE) # levs <- dim.def.ncdf('lev','pressure',levs) var <- var.def.ncdf('data','unitless',list(lon,lat,tdim),-999.9) ncid <- create.ncdf(filename,list(var)) put.var.ncdf(ncid, var, data) close.ncdf(ncid) } ##########################end of function####################### Thank you. Nana Browne ==================================================================== There is no ke...

..._east',lons) lat <- dim.def.ncdf('lat','degrees_north',lats) times <- 1:nt tdim <- dim.def.ncdf('time','days since 1980-01-01', times, unlim=TRUE) # levs <- dim.def.ncdf('lev','pressure',levs) var <- var.def.ncdf('data','unitless',list(lon,lat,tdim),-999.9) ncid <- create.ncdf(filename,list(var)) put.var.ncdf(ncid, var, data) close.ncdf(ncid) } ##########################end of function####################### Thank you. Nana Browne ==================================================================== There is no ke...

Well, I agree that plots with multiple y-axes can be very confusing but .... i am not sure that always they are also misleading .... One time i was asked to make a 2 y-axes plot, one y axes was for elevation (heights in meters) and one for rugosity (values between 1 and 2 - unitless). The idea was to visualize that for a more complex profile the rugosity is higher than for a flatter terrain. A correlation coefficient between elevation and rugosity does not show anything, although depending which formula you use for calculating rugosity, it can nicely correlate with slope. Rugo...

Hi, I have a couple of observations, a question or two, and perhaps a suggestion related to the plotting of density on the y-axis within the hist() function when freq=FALSE. I was using the function and trying to develop an intuitive understanding of what the density is telling me. After reading through this fairly helpful post:

...me<-rel.read.time) filetimes<-c(filetimes,rel.read.time)} #For regular intervals of readings, the code below generates measurement times from the first interval: myfilenames<-row.names(myfileinfo) fileno<-length(myfilenames) intervalue<- myfileinfo$mtime[2] - myfileinfo$mtime[1] unitless.interval<-(as.numeric(intervalue)) ifelse(unitless.interval>=5, hour.interval<-(unitless.interval/60), hour.interval<-unitless.interval) hours<-0 for (i in 1:(fileno-1)){hours<-c(hours,(i*hour.interval))} myfileinfo <- size isdir mode mtime...

...For regular intervals of readings, the code below generates measurement > > times from the first interval: > > > > myfilenames<-row.names(myfileinfo) > > fileno<-length(myfilenames) > > intervalue<- myfileinfo$mtime[2] - myfileinfo$mtime[1] > > > > unitless.interval<-(as.numeric(intervalue)) > > > > ifelse(unitless.interval >=5, hour.interval<-(unitless.interval/60), > > hour.interval<-unitless.interval) > > > > hours<-0 > > > > for (i in 1:(fileno-1)){hours<-c(hours,(i*hour.interval))} >...

....me is a vector with 437270 values, ranging from -4 to 4 with 10 decimal places. # Save as NetCDF #--------------------- dim.time.spi <- dim.def.ncdf("time", "days since 1499-01-01 00:00:00", dim.time) var.spi.24.03.me <- var.def.ncdf("spi03_24_me", "unitless", dim.time.spi, 0, longname="SPI tr_1500_03 24mt MA", prec="float") spi <- create.ncdf("spi_regions_03.nc", var.spi.24.03.me) put.var.ncdf(spi, var.spi.24.03.me, spi24.me) close.ncdf(spi) R prints the following error: #--------------------- Error in put....

Hello, I've read in a thread from this mailing list ( http://lists.xiph.org/pipermail/vorbis-dev/2009-September/020019.html) that the usage of FLOOR1_fromdB_LOOKUP table is to convert Floor1 values from a dB scale to a linear scale. In a dB scale, given a reference value, the other dB values are obtained from it, normally dB_value = 10log(p1/p0), where p0 is the reference value. Supposing p0

...s nothing beyond 'Oooo, packets!', > * that the packets belong to different buckets, that the packets go in > * order, and that packets have position markers. Ogg does not even have > * a concept of 'time'; it only knows about the sequentially increasing, > * unitless position markers. It is up to higher layers which have > * access to the codec APIs to assign and convert units of framing or > * time. TIA for some enlightenment on this. Elaine

...;s multiplexing into a stream. It knows nothing beyond 'Oooo, packets!', that the packets belong to different buckets, that the packets go in order, and that packets have position markers. Ogg does not even have a concept of 'time'; it only knows about the sequentially increasing, unitless position markers. It is up to higher layers which have access to the codec APIs to assign and convert units of framing or time. 3) Given pre-cached decode headers, a player may seek into a stream at any point and begin decode. It may be the case that audio may start after video by a fraction of...

...lear. An example is (date + 1.73) : should one return a true date, which is integer, allow an invalid internal value that is "fixed" at print time, return a numeric, or an error message? I put (timespan/constant) in this category. The author has no hint as to whether the constant is unitless or not. In the medical research environment converstions back and forth from days to months and years are very common, greatly outmassing division of an iterval into pieces, so if I had to guess I would assume that I had to drop the units; another environment might be just the opposite. 4 Respons...

...ranule <p><p>Pfeiffer Expires May 2, 2003 [Page 7] Internet-Draft OGG November 2002 <p> positions"). Ogg does not have a concept of 'time': it only knows about sequentially increasing, unitless position markers. An application can only get temporal information through higher layers which have access to the codec APIs to assign and convert granule positions or time. A specific definition of a media mapping using Ogg may put further constraints on its specific use of the Og...

...ranule <p><p>Pfeiffer Expires May 2, 2003 [Page 7] Internet-Draft OGG November 2002 <p> positions"). Ogg does not have a concept of 'time': it only knows about sequentially increasing, unitless position markers. An application can only get temporal information through higher layers which have access to the codec APIs to assign and convert granule positions or time. A specific definition of a media mapping using Ogg may put further constraints on its specific use of the Og...

...ranule <p><p>Pfeiffer Expires May 2, 2003 [Page 7] Internet-Draft OGG November 2002 <p> positions"). Ogg does not have a concept of 'time': it only knows about sequentially increasing, unitless position markers. An application can only get temporal information through higher layers which have access to the codec APIs to assign and convert granule positions or time. A specific definition of a media mapping using Ogg may put further constraints on its specific use of the Og...

...ranule <p><p>Pfeiffer Expires May 2, 2003 [Page 7] Internet-Draft OGG November 2002 <p> positions"). Ogg does not have a concept of 'time': it only knows about sequentially increasing, unitless position markers. An application can only get temporal information through higher layers which have access to the codec APIs to assign and convert granule positions or time. A specific definition of a media mapping using Ogg may put further constraints on its specific use of the Og...