search for: formlist

Hello, I'm using the following for loop to find regression curves using a list of functions (formList), a list of starting values (startList), uppervalues (upperList) and lower values (lowerList). A sample of the list of function I use in the loop is the following: FormList <- list(PTG.P ~ fz1(Portata, a, b), PTG.P ~ fz2(Portata, a, b), PTG.P ~ fz3(Portata,a, b, d, e), PTG.P ~ fz4(Portata, a,...

..., start=list(a=10, b=10), nls.control(maxiter=200), algorithm='port', trace=TRUE, na.action=na.omit, lower=list(a=0, b=10), upper=list(a=100, b=100)) plotfit(r.PTG.V) I tried to use the function plotfit on the result of the following for loop but I got an error message: for (i in 1:length(formList)) { resultList[[i]] <- nls(formList[[i]], data=subset(dati, Fiume=="Laveggio"), start=startList7[[i]], nls.control(maxiter=1000, warnOnly=TRUE), algorithm='port', na.action=na.omit,lower=lowerList7[[i]], upper=upperList7[[i]]) } plotfit(resultList[[1]] "Erro...

...ature (in > terms of src/main/gram.y, preferably without introducing conflicts) and > its semantics (including the corner cases, some of which you have > already mentioned). I'm not sure I'm up to the task. > If I were doing it, here's what I'd propose: '[' formlist ']' LEFT_ASSIGN expr '[' formlist ']' EQ_ASSIGN expr expr RIGHT_ASSIGN '[' formlist ']' where `formlist` has the syntax of the formals list for a function definition. This would have the following semantics: { *tmp* <- expr # Fo...

.../gram.y, preferably without introducing conflicts) and > > its semantics (including the corner cases, some of which you have > > already mentioned). I'm not sure I'm up to the task. > > > > If I were doing it, here's what I'd propose: > > '[' formlist ']' LEFT_ASSIGN expr > '[' formlist ']' EQ_ASSIGN expr > expr RIGHT_ASSIGN '[' formlist ']' > > where `formlist` has the syntax of the formals list for a function > definition. This would have the following semantics: > > { &g...

...cing > conflicts) and > > its semantics (including the corner cases, some of which you have > > already mentioned). I'm not sure I'm up to the task. > > > > If I were doing it, here's what I'd propose: > > ? ?'[' formlist ']' LEFT_ASSIGN expr > ? ?'[' formlist ']' EQ_ASSIGN expr > ? ?expr RIGHT_ASSIGN? '[' formlist ']' > > where `formlist` has the syntax of the formals list for a function > definition.? This would have the following semantics:...

...> > its semantics (including the corner cases, some of which you have > > > already mentioned). I'm not sure I'm up to the task. > > > > > > > If I were doing it, here's what I'd propose: > > > > '[' formlist ']' LEFT_ASSIGN expr > > '[' formlist ']' EQ_ASSIGN expr > > expr RIGHT_ASSIGN '[' formlist ']' > > > > where `formlist` has the syntax of the formals list for a function > > definition. This would have...

On Sat, 11 Mar 2023 11:11:06 -0500 Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > That's clear, but your proposal violates a very basic property of the > language, i.e. that all statements are expressions and have a value. How about reframing this feature request from multiple assignment (which does go contrary to "everything has only one value, even if it's

...uding the corner cases, some of which you > have > > > > already mentioned). I'm not sure I'm up to the task. > > > > > > > > > > If I were doing it, here's what I'd propose: > > > > > > '[' formlist ']' LEFT_ASSIGN expr > > > '[' formlist ']' EQ_ASSIGN expr > > > expr RIGHT_ASSIGN '[' formlist ']' > > > > > > where `formlist` has the syntax of the formals list for a function > > > defi...

6 ?????? 2023 ?. 22:54:24 GMT+03:00, mikkmart via R-devel <r-devel at r-project.org> ?????: >The pattern of functions accepting other functions as inputs and >passing additional ... arguments to them is prevalent throughout >the R ecosystem. Currently, however, all such functions must one >way or another tackle the problem of inadvertently passing arguments >meant to go to

...: attempt to apply non-function ### is this a bug or desired behavior? Using parenthesis of coures solves the problem. However, I think the operator precedence could be the problem here. I looked at the "./src/main/gram.y" and I think that the line 385 | FUNCTION '(' formlist ')' cr expr_or_assign %prec LOW should be of way higher precedence. But I cannot forsee the side effects of that (which could be horrible in that case). If this is the desired behaviour and not a bug, I'm very interested in the rational behind that. Best wishes, Wilm ps: $ R --ve...

...cing conflicts) and > > > its semantics (including the corner cases, some of which you have > > > already mentioned). I'm not sure I'm up to the task. > > > > > > > If I were doing it, here's what I'd propose: > > > > '[' formlist ']' LEFT_ASSIGN expr > > '[' formlist ']' EQ_ASSIGN expr > > expr RIGHT_ASSIGN '[' formlist ']' > > > > where `formlist` has the syntax of the formals list for a function > > definition. This would have the following sema...

...t; > >? ? ? > already mentioned). I'm not sure I'm up to the task. > > >? ? ? > > > > > > >? ? ?If I were doing it, here's what I'd propose: > > > > > >? ? ? ? ?'[' formlist ']' LEFT_ASSIGN expr > > >? ? ? ? ?'[' formlist ']' EQ_ASSIGN expr > > >? ? ? ? ?expr RIGHT_ASSIGN? '[' formlist ']' > > > > > >? ? ?where `formlist` has the syntax of the formals list fo...

...> already mentioned). I'm not sure I'm up to the task. > > > > > > > > > > > > > If I were doing it, here's what I'd propose: > > > > > > > > '[' formlist ']' LEFT_ASSIGN expr > > > > '[' formlist ']' EQ_ASSIGN expr > > > > expr RIGHT_ASSIGN '[' formlist ']' > > > > > > > > where `formlist` has the syntax of...

...ure I'm up to > > > the task. > > > ???????? > >????? > > > > ???????? > > > > > ???????? > >???? If I were doing it, here's what I'd propose: > > > ???????? > > > > > ???????? > >???????? '[' formlist ']' LEFT_ASSIGN expr > > > ???????? > >???????? '[' formlist ']' EQ_ASSIGN expr > > > ???????? > >???????? expr RIGHT_ASSIGN? '[' formlist ']' > > > ???????? > > > > > ???????? > >???? where `formlis...

...>>>> the task. >>>> ???????? > >????? > >>>> ???????? > > >>>> ???????? > >???? If I were doing it, here's what I'd propose: >>>> ???????? > > >>>> ???????? > >???????? '[' formlist ']' LEFT_ASSIGN expr >>>> ???????? > >???????? '[' formlist ']' EQ_ASSIGN expr >>>> ???????? > >???????? expr RIGHT_ASSIGN? '[' formlist ']' >>>> ???????? > > >>>> ???????? > >???? wh...

...t; is this a bug or desired behavior? Using parenthesis of coures > solves the problem. However, I think the operator precedence could > be the problem here. I looked at the "./src/main/gram.y" and I > think that the line 385 > | FUNCTION '(' formlist ')' cr expr_or_assign %prec LOW > should be of way higher precedence. But I cannot forsee the side > effects of that (which could be horrible in that case). > > If this is the desired behaviour and not a bug, I'm very > interested in the rational behind th...

...ion > > ### > > is this a bug or desired behavior? Using parenthesis of coures solves the > problem. However, I think the operator precedence could be the problem > here. I looked at the "./src/main/gram.y" and I think that the line 385 > | FUNCTION '(' formlist ')' cr expr_or_assign %prec LOW > should be of way higher precedence. But I cannot forsee the side effects > of that (which could be horrible in that case). > > If this is the desired behaviour and not a bug, I'm very interested in the > rational behind that. > > Be...

Hello, I'm a beginner with R and it's the first time I'm using the R-help list... I hope I'm in the right place, if not: Sorry!! I need to do non linear regressions on a data set which columns are: "river.name" "Portata" "PTG.P" "PO4.P" "NT.N" "NH4.N" "NO3.N" "BOD5" "SiO2"

...t;> >> is this a bug or desired behavior? Using parenthesis of coures solves the >> problem. However, I think the operator precedence could be the problem >> here. I looked at the "./src/main/gram.y" and I think that the line 385 >> | FUNCTION '(' formlist ')' cr expr_or_assign %prec LOW >> should be of way higher precedence. But I cannot forsee the side effects >> of that (which could be horrible in that case). >> >> If this is the desired behaviour and not a bug, I'm very interested in >> the rational behin...

...', ''), ('__failure_expire_time', ''), ('__max_restarts', ''), ('__restart_expire_time', ''), ('root_elem', 'esvc_root'), ('action', 'edit'), ('res_count', '1'), ('form_xml', '<formlist><form id="res_0" parent="esvc_root"><input name="parent_id" value="esvc_root" type="hidden"/><input name="form_id" value="res_0" type="hidden"/><input name="type" value="vm" t...