search for: confind

Displaying 5 results from an estimated 5 matches for "confind".

Did you mean: confid
2012 Sep 25
1
calculation of diversity confidence interval
...perately for a test which is calculating confidence intervals from diversity measurements (non-normaly distributed) (fishers alpha diversity). I was checking the package "vegan" but there seems to be nothing useful. Does anyone of you know with what package I easily could calculate such a confindence interval? Best, Mike
2008 Jun 25
1
confidence bounds using contour plot
Hello I'm trying to calculate 2d confindence bounds into a scatterplot using the function "kde2d" (package MASS) and a contour plot. I found a similar post providing a solution - unfortunatly I do not realy understand which data I have to use to calculated the named "quantile": Post URL: http://tolstoy.newcastle.edu....
2007 Feb 21
1
Confindence interval for Levenberg-Marquardt fit
Dear all, I would like to use the Levenberg-Marquardt algorithm for non-linear least-squares regression using function nls.lm. Can anybody help me to find a a way to compute confidence intervals on the fitted parameters as it is possible for nls (using confint.nls, which does not work for nls.lm)? Thank you for your help Michael
2019 Jan 15
2
Reducing the number of ptrtoint/inttoptrs that are generated by LLVM
...we can define >> llvm.psub(p,q) as poison. >> Other than meeting C specification, correctness of llvm.psub is tested >> with SPEC CPU2017 and LLVM Nightly Tests as well. >> > > SPEC and the nightly test suite are great at finding problems, but quite > bad at giving confindence that there are not problems. For subtle things > like this, I would expect you need to look an a much larger sampling of > real-world application code. > > >> >> But it is true that sometimes pointer subtraction is used to get distance >> between two objects. >&...
2019 Jan 14
4
Reducing the number of ptrtoint/inttoptrs that are generated by LLVM
Hello Chandler, > First and foremost - how do you address correctness issues here? Because the subtraction `A - B` can escape/capture more things. Specifically, if one of `A` or `B` is escaped/captured, the > subtraction can be used to escape or capture the other pointer. So *some* of the conservative treatment is necessary. What is the plan to update all the analyses to remain correct?