Sent from my iPhone
> On Jan 19, 2025, at 1:57 PM, David Winsemius wrote:
>
> I don’t understand why you don’t include the full text of the error.
>
> —
> David
> Sent from my iPhone
>
>> On Jan 19, 2025, at 10:00 AM, Sparks, John via R-help
>> wrote:
>>
>> Hello R-Helpers,
>>
>> I was
I don’t understand why you don’t include the full text of the error.
—
David
Sent from my iPhone
> On Jan 19, 2025, at 10:00 AM, Sparks, John via R-help
> wrote:
>
> Hello R-Helpers,
>
> I was looking into how to test whether the beta coefficient from a regression
> would be the same for
Hello R-Helpers,
I was looking into how to test whether the beta coefficient from a regression
would be the same for two different groups contained in the dataset for the
regression.
When I put that question into google, AI returned a very nice looking answer
(and a couple of variations on it)
I am afraid my errors are worse! (so are my postings. I should have
given an example.)
```
x <- 1
y <- 2
nofunction("something stupid I am doing!")
z <- 4
```
and
```
> source("where-is-my-water.R")
Error in nofunction("something stupid I am doing!") :
could not find function "nofunction"
``
On 2025-01-18 6:41 p.m., Ivo Welch wrote:
I often find myself hunting where in my program an error has happened,
(of course, in R, many error messages are mysterious in themselves,
too, making it even harder.) the way I do it is mostly with inserting
`message()` statements.
what I would really
I recommend making sure your code is built with functions and using the
debugger and breakpoints (e.g. [1]) to follow the flow of the code to lead you
to where your problem is.
If you are used to building thousand-line top-level scripts then you might not
welcome this suggestion, but in that yo
Hi Ivo,
I maintain 'package:this.path' that I believe does what you want. I
regularly add this to my own code when I need to:
warning(sprintf("remove this later at %s#%d",
this.path::try.this.path(), this.path::LINENO()), call. = FALSE,
immediate. = TRUE)
Of course, modify as needed.
Regards,
great. wonderful. will check it out, and hopefully widely recommend
it (to my students, too). Non-descriptive R error messages have had
most of our school abandon R in favor of python. :-(
On Sat, Jan 18, 2025 at 3:46 PM Iris Simmons wrote:
>
> Hi Ivo,
>
>
> I maintain 'package:this.path' tha
I often find myself hunting where in my program an error has happened,
(of course, in R, many error messages are mysterious in themselves,
too, making it even harder.) the way I do it is mostly with inserting
`message()` statements.
what I would really like to have is a parser that inserted 'curl
You may also want to check out forum.posit.co/
On Wed, 15 Jan 2025 at 14:14, Marc Schwartz via R-help
wrote:
> Hi Eliana,
>
> It is not clear which application is causing the error.
>
> As you are running macOS 13.3 (Ventura) and that you are trying to install
> both R and RStudio (two separate
10 matches
Mail list logo
