Bug #4081
closedRework Appendix B
Added by Chad Berkley over 15 years ago. Updated over 14 years ago.
0%
Description
Rework Appendix B of the User Manual for the 2.0
release.
Related issues
Updated by Chad Berkley over 14 years ago
Updated links, proof-read. Need NCEAS links to work. Sent email to shaun and rick asking about missing pdfs.
http://www.nceas.ucsb.edu/scicomp/Dloads/RCourse/PeterAdlerRCheatSheet.pdf
http://www.nceas.ucsb.edu/scicomp/Dloads/RProgramming/AnIntroToR.pdf
http://www.nceas.ucsb.edu/scicomp/RProgTutorialsLatest.html
Updated by Chad Berkley over 14 years ago
updated links to NCEAS R reference material. Links are as follows (thanks, Rick).
http://www.nceas.ucsb.edu/scicomp/rtutorialslatest
http://cran.r-project.org/doc/manuals/R-intro.pdf
http://www.nceas.ucsb.edu/files/scicomp/Dloads/RCourse/PeterAdlerRCheatSheet.pdf
http://cran.r-project.org/doc/contrib/Short-refcard.pdf
http://pj.freefaculty.org/R/Rtips.html
Waiting for Ben to review this section for any additional functionality, then this will be done.
Updated by ben leinfelder over 14 years ago
Reviewed the R appendix - some minor typos corrected, but no glaring omissions re: functionality. I was concerned about the BEAM example not going to run - but it still executes successfully.
As discussed with Chad, we need to be aware of how the R examples are included in the installed version of Kepler 2.0. A handful of workflows reference data files that are in the 'r' module ('r-2.0' for this release). It would be nice to not have to rework the examples each time we release the module (r-2.1, say)
Also, there are references made to the R demo directory in the text of the manual - we want to make sure those reflect what's in the installer for 2.0
Last thing: should we re-do screen shots so that the 2.0 changes to the GUI (mostly in the component search area) are reflected? I have not done this because I didn't want to introduce OS X shots in the mix of Linux (or are they Windows?) shots. Or do we not care about them being consistent?
Updated by Chad Berkley over 14 years ago
Originally, I had wanted to keep all of the screen shots consistent, however, it's going to take a lot of work to do that. What do people think of mixing screen shots from various OSs?
Updated by debi staggs over 14 years ago
(In reply to comment #4)
Originally, I had wanted to keep all of the screen shots consistent, however,
it's going to take a lot of work to do that. What do people think of mixing
screen shots from various OSs?
I agree with Matt, that is is probably o.k., and it shows that we support different OS's. Also, so far what I have found in replacing the screen shots is that there are many that just show the workflow canvas by itself and those don't have to be replaced. The ones that all DO need updating are any that show the component / data / outline panel, since the extra tab has been added, the search looks different, and the toolbar no longer has the full screen button in it.
Updated by debi staggs over 14 years ago
(In reply to comment #5)
(In reply to comment #4)
Originally, I had wanted to keep all of the screen shots consistent, however,
it's going to take a lot of work to do that. What do people think of mixing
screen shots from various OSs?I agree with Matt, that is is probably o.k., and it shows that we support
different OS's. Also, so far what I have found in replacing the screen shots
is that there are many that just show the workflow canvas by itself and those
don't have to be replaced. The ones that all DO need updating are any that
show the component / data / outline panel, since the extra tab has been added,
the search looks different, and the toolbar no longer has the full screen
button in it.
Also, I don't mind taking on the task of doing the screen shots for the rest of the docs. If that will be helpful.
Updated by Chad Berkley over 14 years ago
Ok, thanks, Debi. The only thing left to do on this is update screenshots then. I've made a separate bug (bug 4867) for screenshots so I'm closing this one.