This is the top level aggregation page for our information about setting up computers for scientific research.
We keep guides for users that have Windows, Macintosh, and Linux computers, until now they have floated about in crmda.ku.edu. Now, we have one page to rule them all.
Maintaining Personal Computer Systems
Windows: Our admin overview webpage is https://crmda.ku.edu/windows-admin-tips.
Macintosh: Our overview webpage is https://crmda.ku.edu/mac-admin-tips.
Program-specific setup pages
We also have software-specific guides for many programs. It seems likely that, in the long run, the content we offer will be moved into these program-specific pages and the
Recently, we created CRMDA Guide 46, the "Windows R Setup" setup page. That is a "just get it done" information package, including a slide show and a screencast of the slide show. That's the "Cliffs Notes" version, if you want details, the Windows admin tips page is the right place to be.
The "Mac R Setup" slide show and voiceover will be offered as CRMDA Guide 47.
The LaTeX page: https://crmda.ku.edu/latex-help.
Git and GitLab
Preparing for Workshops
When we offer workshops, we hope participants will bring their own computers. Usually, software installation, and some system re-configuration is required in order to participate fully in a presentation about R, LaTeX, Mplus, or whatnot.
1. Use a "real computer", not a cell phone, Ipad (or most tablet devices). Users generally need a "full fledged computer", something that has a reasonably current version of Mac OSX, Windows, or Linux. We run into problems with Android tablets and Windows Surface devices because the screens are too small and the OS tries to block us from having several windows open at once.
2. Do software downloads ahead of time. Don't wait until you arrive for the workshop, especially if you are using software that requires a long, intricate install process. This is especially true for the LaTeX distributions like macTeX, TeXLive or MikTek. The guide documents above will provide addresses from which software can be downloaded.
3. Try to do installs ahead of time. Keep notes on what you do, so that we might fix problems more easily. The R support pages offer detailed, step by step information on the installation.
4. Our guides will generally include an example command to test the installed software. Try to run the same command and we can compare our results with yours.