Displaying 5 results from an estimated 5 matches for "int_values".
2008 Mar 20
1
Use of Factors
...# fill the SubjID
interp_out[,1]=SubjID;
Now fill in interplated values for each visit.
interp_out[1:9,4]=hrv1;interp_out[10:18,4]=hrv2;
# hrv1 & hrv2 come from the following function, the "lm" parameter is
output from the standard lm() function:
interpolateToXL = function(lm,maxxl){
int_values=matrix(nrow=9,ncol=1)
int_values[1,]=coef(lm)[1];
if (maxxl>25)
int_values[2,]=coef(lm)[1]+coef(lm)[2] * 25
if (maxxl>50)
int_values[3,]=coef(lm)[1]+coef(lm)[2] * 50
if (maxxl>75)
int_values[4,]=coef(lm)[1]+coef(lm)[2] * 75
if (maxxl>100)
int_values[5,]=coef(lm)[1]+coef(lm)[2] *...
2007 May 03
2
[patch] Mac Universal Binaries
On 5/3/07, Erik de Castro Lopo <mle+la@mega-nerd.com> wrote:
> Peter Grayson wrote:
>
> Personally I think universal binaries are a bad idea.
They have obviously served some purpose, but I tend to agree that the
concept does not seem to scale well once outside the Apple microcosm.
> For one of my projects, libsndfile, endian issues is not the only
> think that breaks in
2007 May 03
0
[patch] Mac Universal Binaries
Peter Grayson wrote:
> Can you elaborate on what kind of CPU vagaries come into play besides
> endianess?
One issue I found was the cpu behaviour when converting from
float/double to int32 when the source float is outside the range
of values that can be represented by the int32.
For instance:
float int32_ppc in32_x86
2147483649.0 2147483647 -2147483648
2007 May 03
2
[patch] Mac Universal Binaries
> One issue I found was the cpu behaviour when converting from
> float/double to int32 when the source float is outside the range
> of values that can be represented by the int32.
>
> For instance:
>
> float int32_ppc in32_x86
> 2147483649.0 2147483647 -2147483648
> 2147483648.0 2147483647 -2147483648
> 2147483647.0
2019 May 07
1
samba-tool max-pwd-age error
On Tue, 7 May 2019 17:06:24 +1200
Tim Beale <timbeale at catalyst.net.nz> wrote:
> Apologies, this bug fell through the cracks and the fix never got
> backported to 4.10. I've uploaded the backport to the bug now, it just
> needs a review signoff.
>
> To recap, it was introduced as a side-effect of switching to Python 3.
> The old code never worked as intended on