Displaying 20 results from an estimated 21 matches for "expr10".
Did you mean:
expr1
2007 May 26
1
bug from nlm function (PR#9711)
...b)-(a-1)*(log(x)-log(b))- (x^a)/(b^a))
> fllwfuncH <-deriv(fllwform,c("a","b"),function(a,b,x){})
> fllwfuncH
function (a, b, x)
{
.expr2 <- log(b)
.expr4 <- a - 1
.expr5 <- log(x)
.expr6 <- .expr5 - .expr2
.expr9 <- x^a
.expr10 <- b^a
.expr19 <- .expr10^2
.expr23 <- 1/b
.value <- log(a) - .expr2 - .expr4 * .expr6 - .expr9/.expr10
.grad <- array(0, c(length(.value), 2), list(NULL, c("a",
"b")))
.grad[, "a"] <- 1/a - .expr6 - (.expr9 * .expr5...
2001 Oct 05
1
nls() fit to a lorentzian - can I specify partials?
...f my expression? (I suspect
it's doing derivatives numerically)
Can I specify the partials in advance?
I noticed the 'deriv' function, but am baffled by its output:
> deriv(~ a0 / (Q*sqrt((1-(x/f0)^2)^2 + ((x/f0) * 1/Q)^2)),"a0")
expression({
.expr1 <- x/f0
.expr10 <- Q * sqrt(1 - .expr1^2^2 + .expr1 * 1/Q^2)
.value <- a0/.expr10
.grad <- array(0, c(length(.value), 1), list(NULL, c("a0")))
.grad[, "a0"] <- 1/.expr10
attr(.value, "gradient") <- .grad
.value
})
I think .expr10 should look more l...
2023 Jan 09
5
return value of {....}
...ession evaluated. This has the visibility of the last evaluation.
But both x AND y are created, but the "return value" is y. How can this be advantageous for solving practical problems? Specifically, consider the following code:
F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
Both expr5 and expr7 are created, and are accessible by the code outside of the nested braces right? But the "return value" of the nested braces is expr7. So doesn't this mean that only expr7 should be accessible? Please help me entangle this (of course the return value of F is expr...
2001 May 30
2
environments
I would like to be able, inside a function, to create a new function, and
use it as part of a formula as an argument to, say, gnls or nlme. for
example:
MyTop <- function(data=dta) {
Cexp <- function(dose,A,B,m){...}
Model <- as.formula(paste("y","~ Cexp(",paste(formals(Cexp),collapse
=", "),")"))
MyCall <-
2023 Jan 09
2
return value of {....}
...he visibility of the last evaluation.
>
> But both x AND y are created, but the "return value" is y. How can this be
> advantageous for solving practical problems? Specifically, consider the
> following code:
>
> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
>
> Both expr5 and expr7 are created, and are accessible by the code outside
> of the nested braces right? But the "return value" of the nested braces is
> expr7. So doesn't this mean that only expr7 should be accessible? Please
> help me entangle this (of course the r...
2023 Jan 11
1
return value of {....}
...he visibility of the last evaluation.
>
> But both x AND y are created, but the "return value" is y. How can this be
> advantageous for solving practical problems? Specifically, consider the
> following code:
>
> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
>
> Both expr5 and expr7 are created, and are accessible by the code outside
> of the nested braces right? But the "return value" of the nested braces is
> expr7. So doesn't this mean that only expr7 should be accessible? Please
> help me entangle this (of course the r...
2023 Jan 09
3
return value of {....}
...This has the visibility of the last evaluation.
>
> But both x AND y are created, but the "return value" is y. How can this be advantageous for solving practical problems? Specifically, consider the following code:
>
> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
>
> Both expr5 and expr7 are created, and are accessible by the code outside of the nested braces right? But the "return value" of the nested braces is expr7. So doesn't this mean that only expr7 should be accessible? Please help me entangle this (of course the return value of...
2023 Jan 09
1
return value of {....}
...is has the visibility of the last evaluation.
>
> But both x AND y are created, but the "return value" is y. How can this be advantageous for solving practical problems? Specifically, consider the following code:
>
> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
>
> Both expr5 and expr7 are created, and are accessible by the code outside of the nested braces right? But the "return value" of the nested braces is expr7. So doesn't this mean that only expr7 should be accessible? Please help me entangle this (of course the return value of...
2023 Jan 09
1
return value of {....}
...t evaluation.
>>
>> But both x AND y are created, but the "return value" is y. How can this
>> be advantageous for solving practical problems? Specifically, consider the
>> following code:
>>
>> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
>>
>> Both expr5 and expr7 are created, and are accessible by the code outside
>> of the nested braces right? But the "return value" of the nested braces is
>> expr7. So doesn't this mean that only expr7 should be accessible? Please
>> help me entangle t...
2023 Jan 12
4
return value of {....}
...ibility of the last evaluation.
>>
>> But both x AND y are created, but the "return value" is y. How can this be advantageous for solving practical problems? Specifically, consider the following code:
>>
>> F <- function(X) {? expr; expr2; { expr5; expr7}; expr8;expr10}
>>
>> Both expr5 and expr7 are created, and are accessible by the code outside of the nested braces right? But the "return value" of the nested braces is expr7. So doesn't this mean that only expr7 should be accessible? Please help me entangle this (of course the return v...
2023 Jan 09
1
return value of {....}
...t;
>>> But both x AND y are created, but the "return value" is y. How can this
>>> be advantageous for solving practical problems? Specifically, consider the
>>> following code:
>>>
>>> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
>>>
>>> Both expr5 and expr7 are created, and are accessible by the code outside
>>> of the nested braces right? But the "return value" of the nested braces is
>>> expr7. So doesn't this mean that only expr7 should be accessible? Please
>>>...
2023 Jan 09
1
return value of {....}
...last evaluation.
> >
> > But both x AND y are created, but the "return value" is y. How can this
> be advantageous for solving practical problems? Specifically, consider the
> following code:
> >
> > F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
> >
> > Both expr5 and expr7 are created, and are accessible by the code outside
> of the nested braces right? But the "return value" of the nested braces is
> expr7. So doesn't this mean that only expr7 should be accessible? Please
> help me entangle this (of co...
2023 Jan 13
1
return value of {....}
....
> >>
> >> But both x AND y are created, but the "return value" is y. How can this
> be advantageous for solving practical problems? Specifically, consider the
> following code:
> >>
> >> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
> >>
> >> Both expr5 and expr7 are created, and are accessible by the code
> outside of the nested braces right? But the "return value" of the nested
> braces is expr7. So doesn't this mean that only expr7 should be accessible?
> Please help me entangle thi...
2023 Jan 09
1
return value of {....}
...This has the visibility of the last evaluation.
>
> But both x AND y are created, but the "return value" is y. How can this be
advantageous for solving practical problems? Specifically, consider the
following code:
>
> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
>
> Both expr5 and expr7 are created, and are accessible by the code
> outside of the nested braces right? But the "return value" of the
> nested braces is expr7. So doesn't this mean that only expr7 should be
> accessible? Please help me entangle this (of course th...
2023 Jan 15
3
return value of {....}
....
> >>
> >> But both x AND y are created, but the "return value" is y. How can this
> be advantageous for solving practical problems? Specifically, consider the
> following code:
> >>
> >> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
> >>
> >> Both expr5 and expr7 are created, and are accessible by the code
> outside of the nested braces right? But the "return value" of the nested
> braces is expr7. So doesn't this mean that only expr7 should be accessible?
> Please help me entangle thi...
2023 Jan 10
1
return value of {....}
...This has the visibility of the last evaluation.
>
> But both x AND y are created, but the "return value" is y. How can this be
advantageous for solving practical problems? Specifically, consider the
following code:
>
> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
>
> Both expr5 and expr7 are created, and are accessible by the code
> outside of the nested braces right? But the "return value" of the
> nested braces is expr7. So doesn't this mean that only expr7 should be
> accessible? Please help me entangle this (of course the r...
2023 Jan 10
1
return value of {....}
...This has the visibility of the last evaluation.
>
> But both x AND y are created, but the "return value" is y. How can this be
advantageous for solving practical problems? Specifically, consider the
following code:
>
> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
>
> Both expr5 and expr7 are created, and are accessible by the code
> outside of the nested braces right? But the "return value" of the
> nested braces is expr7. So doesn't this mean that only expr7 should be
> accessible? Please help me entangle this (of course th...
2023 Jan 16
1
return value of {....}
....
> >>
> >> But both x AND y are created, but the "return value" is y. How can this
> be advantageous for solving practical problems? Specifically, consider the
> following code:
> >>
> >> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
> >>
> >> Both expr5 and expr7 are created, and are accessible by the code
> outside of the nested braces right? But the "return value" of the nested
> braces is expr7. So doesn't this mean that only expr7 should be accessible?
> Please help me entangle thi...
2005 Nov 09
1
strategies to obtain convergence using nlme
...then use the fixed effect values from nlsList (i.e. the average
value of each parameter over the groups) to do a nonlinear mixed model
(nlme) using the fixed effects estimates from nlsList, I fail to
converge after 50 iterations and get two types of warning:
(1): "NaNs produced in: sqrt(.expr10)" - this is because the parameter
values drift into regions in which the sqrt in the function is
undefined.
(2) "Singular precision matrix in level -1, block 1". - I do not know
what this warning means.
I have tried many different changes in the starting values and none
work....
2023 Jan 16
2
return value of {....}
....
> >>
> >> But both x AND y are created, but the "return value" is y. How can this
> be advantageous for solving practical problems? Specifically, consider the
> following code:
> >>
> >> F <- function(X) { expr; expr2; { expr5; expr7}; expr8;expr10}
> >>
> >> Both expr5 and expr7 are created, and are accessible by the code
> outside of the nested braces right? But the "return value" of the nested
> braces is expr7. So doesn't this mean that only expr7 should be accessible?
> Please help me entangle thi...