This page is a collection of known issues and bugs that you may find when working with Red-R. These issues are being looked into and in some cases may have comments below them that explain the problem and solution in more detail.

Issues and Bugs:

Red-R Canvas and Widgets Show “(Not Responding)”:

• This seems to be a problem with the way that python interacts with R. We have attempted to embed R in a thread so that this will not happen, however, if you are performing a very time consuming function then you might see this. If you know that the function you are performing takes a long time you should ignore this and NOT click the Red-R canvas, that just makes the problem worse. Instead just wait for the widget to finish. If you aren’t sure if Red-R really has a problem one easy way to check is to open the task manager in Windows and check if Red-R (called python.exe in the task manager) is doing anything and if the application is taking up more memory over time. This usually indicates that Red-R is working and is just processing your data.
• We see this problem from time to time particularly when loading a complicated saved widget schema and with Read CEL Files and Present Calls.

I sometimes see an error that says unexpected end of input when I am using formula entry.

• R requires that names of columns be of a certain format to search for them in a formula.  If your column name begins with a number then you will get this error.
• To avoid this you should use Name Protector to convert your names to R – compliant names.
• See the video tutorial on nameProtector for more information.

rpy error at line 105

• We have seen this problem occurring in the compiled version of Red-R. It appears to be caused when rpy attempts to print it’s output to the standard output. We have set printing from rpy to be deactivated in newer releases. The problem should be fixed in Red-R version 1.7.

DON’T PANIC!!!

From time to time you may see a terrible error message pop up on your screen followed by some output window that has lots of code in it.

More often than not this is caused by an error in R code. This is the same error that would happen if you made a syntax error in R. The session is till running and you can still use Red-R. Don’t worry. Just try to do what you were doing again and see if there is an error message in the widget.

More than likely you just have some default setting that doesn’t match your data and the widget didn’t check for this before sending the command to R. Do the developer a favor and let her know that there is this error and she should check for these things in the next package release.