R 7q Solve For Q

[Kerby Kolpack]

I think it might be something to do with the file path to the library where installed packages go? I'm using both the latest version of R and R Studio, 64-bit, and using Canada's U of T CRAN mirror site.

What does "non-zero exit status" mean? Is it trying to find a library for the installation?> The appData file mentioned in the code doesn't seem to exist or I cannot access it. How do I change it to another local folder?

A non-zero exit status means in this case that the system failed to install the package. There seem to be a number of unresolved dependencies in the installation process. You could try to resolve this by attempting to install the package using the option dependencies=TRUE; like this:

i was struggling with the same problem, for a long time and mikes solution didnt help me either. I tried everything upto reinstalling R. Still didnt work.However the solution is quite simple in my case. In the Terminal dont run R as R but use:

Several of my students have been having problems like this with R3.3.3 (Mac) and R3.5.0 (all). We found that installing devtools and loading packages from github helped get beyond the odd "non zero exit status" problems, e.g. to get the C50 package at :

The R-7 was 34 m (112 ft) long, 10.3 m (34 ft) in diameter and weighed 280 metric tons (280 long tons; 310 short tons); it had a single stage with four strap on boosters powered by rocket engines using liquid oxygen (LOX) and kerosene and capable of delivering its payload up to 8,000 km (5,000 mi), with an accuracy (CEP) of around 5 km (3.1 mi). A single thermonuclear warhead was carried with a nominal yield of 3 megatons of TNT. The launch was boosted by four strap-on liquid rocket boosters with a central 'sustainer' engine powering the central core. Each strap-on booster included two vernier thrusters and the core stage included four. The guidance system was inertial with radio control of the vernier thrusters.[1]

The rocket had some key features to it that made it unique. Instead of using jet vanes for control, which increased resistance generated at the engine nozzle exhaust outlet, the R-7 used special control engines for steering. These same engines served as the last stage's vernier thrusters.[9] Because of clustered design, each booster had its own propellant tanks. The design team had to develop a system to regulate the propellant component consumption ratio and to synchronize the consumption between the boosters.[10]

Instead of a free-standing missile which was launched from a horizontal pad, it turned out that assembling a cluster of a central core and four boosters on the pad is almost impossible without it falling apart. Also, a wind gust could knock the unfuelled missile off of the pad. The solution was to eliminate the pad and to suspend the entire rocket in the trusses that bear both vertical weight load as well as horizontal wind forces. The launch system simulated flight conditions with strap-on boosters pushing the central core forward.[11]

The existing testing site at Kapustin Yar was inadequate for the testing required for the R-7. Therefore a new site in Kazakhstan was approved on the 12 February 1955, that would eventually become the Baikonur Cosmodrome.[12] The first series of test commenced when a flight-ready vehicle was delivered on 1 May 1957, and flown on 15 May. A fire broke out in one of the strap-on boosters almost immediately at liftoff. The missile broke away from the booster at T+88 seconds, which crashed 400 km (248 miles) downrange. The next attempt on 11 June an electrical short caused the missile to start rolling uncontrollably and disintegrate 33 seconds after liftoff.[13]

The second test series incorporating improvements commenced on the 24 December 1958 and concluded on the 27 December 1959. Seven of the eight test launches were successful. Problems were resolved during these intensive tests and the missile was declared operational on the 20 January 1960.[16]

The first strategic-missile unit went on alert status on 15 December 1959 at Plesetsk in the north-west of the USSR. An improved version, the R-7A with a lighter warhead, all inertial guidance system and a range of 12,000 km, became the standard version once it reached operational status on the 12 September 1960.[16][18]

The costs of the system were high, mostly due to the difficulty of constructing in remote areas the large launch sites required. Besides the cost, the missile system faced other operational challenges. With the U-2 overflights, the huge R-7 launch complexes could not be hidden and therefore could be expected to be destroyed quickly in any nuclear war. Also, the R-7 took almost twenty hours to prepare for launching, and it could not be left on alert for more than a day due to its cryogenic fuel system. Therefore, the Soviet force could not be kept on permanent alert and could have been subject to an air strike before launching. These issues meant that the original planned fifty launch complexes were reduced to six, five for strategic forces, Site 31 at Baikonur and Sites 16, 41 and 43 (2 pads) at Plesetsk and one for space launches at Site 1, Baikonur.[16][19]

The limitations of the R-7 pushed the Soviet Union into rapidly developing second-generation missiles which would be more viable weapons systems, particularly the R-16.[20] The R-7 was phased out of military service by mid 1968.[21]

I'm glad you are trying to understand how it all works! In the long run, that will make you a more confident R user. You might want to read this: Differentiating R from RStudio. Under normal circumstances, package installation doesn't have anything to do with your version of RStudio, but it can have a lot to do with your version of R.

Also the operating system. Linux systems install from the source code and unless you get a message "Error ... non-zero exit status," you're ok. On Mojave, you sometimes have to install from source, but usually it's precompiled binaries, so you see that less often.

jcblum,
is the below the correct way to include the info??? I started from the very beginning and then session info... not sure whether to do both.
I am going to read the differentiating r from r studio now

The short answer is: you will be much happier if you upgrade your R to the latest version (3.5.1) and then try installing everything again. Because you are on a two-year-old version of R, newer versions of the packages you are trying to install are not available as easy-to-install pre-compiled binaries, and instead must be compiled from source. R is trying to do this, but your computer does not have the proper tools installed. If you update R, then binaries will be available and things will suddenly get a lot easier!

jcblum
your instructions were on perfect level for me to follow. I have been using r studio only because it is not as scary looking. I never thought they may be linked in anyway. I am following instructions now and hope this solves issues. I have been trying stuff for about month and half now and very insecure in my knowledge and ability. thanks so much for your clarity.
if you do not mind I will reply when all steps are followed. I am doing laundry so I may need to step out for bit.
stephen

When installing or updating packages, you may get a message that a later version is available in source form. You will run into difficulties if you haven't installed the latest XCode App (free) from the App Store and then issued the terminal command

That will work most of the time, but there are a few source packages that won't compile without some serious under-the-hood work best avoided unless you want to do a lot of tinkering with clang, gcc and different flavors and combinations of settings. I used to have to do a lot of that kind of stuff and it can easily consume a day, so I avoid it and just wait until Saint Simon Urbanek does it for us.

You're welcome! Follow-up questions (or reports of spectacular success ) are welcome! The system administration aspects of R are one of the steeper parts of the learning curve, and a common source of trouble for newcomers.

FYI, a new version of R is released every year, usually in April. Pre-compiled binaries of packages are only created for the latest version of R and (often) latest-minus-1. So it's usually a good idea to keep your R installation up to date.

In case you're wondering what this is about, Simon Urbanek is the person who compiles all the R package binaries for Mac that are posted to CRAN. It's a big job, and he does it as a volunteer, hence the sainthood .

so far I have found quick and easy success: ggplot installed w its dependencies and I used it to do a quick and pretty grap, which I saved you from having to see, although I wouldn't be sure how to include it.
I had to install and load hexbin.
I think I am understanfding that I will need to install each package I have used so far?
thanks so much for your help.

no, that will not be a problem at all. and small price to pay if I can get everything running smooth.
I hate to piggyback, but I am going to and let me know if you can help, or I will post a new topic as I am hab=ving another sore spot for days and it is preventing forward movement: I am following a book and it is telling me to use RMysql to work btwn r and MySQL. I just can never connect: the following error. I have signed into MySQL thru terminal w success with this suer and password.
it is my understanding thta RMysql is being replaced. could this be an issue? should I just skip thes instructions from a book a few years old and use new package for MySQl?

When we have a function in formula form, it is usually a simple matter to evaluate the function. For example, the function [latex]f\left(x\right)=5 - 3x^2[/latex] can be evaluated by squaring the input value, multiplying by 3, and then subtracting the product from 5.

If [latex]\left(p+3\right)\left(p - 1\right)=0[/latex], either [latex]\left(p+3\right)=0[/latex] or [latex]\left(p - 1\right)=0[/latex] (or both of them equal 0). We will set each factor equal to 0 and solve for [latex]p[/latex] in each case.

c80f0f1006