Debugging of R script

Question

I have a script written on Basic, that get on input CSV-file and compute collision between random splitting of input data. This script is here. I need to reimplement it on R. I've written such script. Here is input data.

But in condition

if(nentries==nrows*ncolumns)    
{  
    print("Columns, rows, and entries check; we're good to go.")  
}  
else  
{  
    print("Columns, rows, and entries don't check; please look at your data file to make sure each line has equal no. of entries.")  
}

appear error

source("path\\to\\script.r")
error in source("path\\to\\script.r") : 
D:\projects\basicToR\target.r:19:1: Unexpected 'else'
18:         }
19: else
    ^

Why is the error here? And is there other errors in R file?

UPDATE I've forgotten write in question about error

Error in seq.default(1, firstsofar, 1) : Invalid sign 'by' argument

in fragment of code

for (q in seq(1,firstsofar,1)) {
    if( randnum[i]==randnum[q]) {taken="yes"}
}

As for your edit, it's completely unrelated to your original question, so to get an answer you should start a new question. But it sounds like `firstsofar` took a value less than 1, so that the 3rd argument `by=1` that you've given is the wrong sign (positive, not negative) to get the sequence there. — Gregor Thomas, Feb 02 '13 at 19:53

Dason · Answer 1 · 2013-02-02T17:52:22.963

Rewrite that as

if(nentries==nrows*ncolumns)    {
     print("Columns, rows, and entries check; we're good to go.")
}else{
     print("Columns, rows, and entries don't check; please look at your data file to make sure each line has equal no. of entries.")
}

You need to have the else on the same line as the closing brace for the 'if'

From the R Language Definition

The else clause is optional. The statement if(any(x <= 0)) x <- x[x <= 0] is valid. When the if statement is not in a block the else, if present, must appear on the same line as the end of statement2. Otherwise the new line at the end of statement2 completes the if and yields a syntactically complete statement that is evaluated. A simple solution is to use a compound statement wrapped in braces, putting the else on the same line as the closing brace that marks the end of the statement.

score 2 · Accepted Answer · answered Feb 02 '13 at 17:37

2

For reasons I don't entirely understand, R freaks out when else isn't on the same line as the closing curly bracket before it. Try:

if(nentries==nrows*ncolumns)    {
     print("Columns, rows, and entries check; we're good to go.")
}else{
     print("Columns, rows, and entries don't check; please look at your data file to make sure each line has equal no. of entries.")
}

answered Feb 02 '13 at 17:37

2

It is the REPL -- line-by-line parsing. – Dirk Eddelbuettel Feb 02 '13 at 17:57
2

The reason is that R code is run one line at a time, whether you're at the console or not. It's the same reason you can enter (at the `>` console) `> 1 +` and then `> 2`, but not `> 1` `> + 2` – Gregor Thomas Feb 02 '13 at 17:57
Thanks, @DirkEddelbuettel and shujaa for the clarification. – Feb 02 '13 at 18:11
@shujaa Bad example - you totally can do `> 1` and then `> + 2`. It's not the same as `> 1 +` then `> 2` but you can do it ;) – Dason Feb 02 '13 at 22:42
@Dason guess I'll use division next time ;) – Gregor Thomas Feb 02 '13 at 23:42

Debugging of R script

2 Answers2