@acer correctly identified the problem - dsolve format for  a numeric solution, assuming you want a list of procedures, is:

  dsolve( { sequence of equations }, numeric, output = listprocedure )

where the sequence of equations is the odes and the conditions. 

But, allow me one other suggestion. I you are going to use subscripts, do NOT use indexed variables. Instead, use atomic variables. For example, instead of 

   R[V] := 0.72 * AU;

write:

  R__V := 0.72 * AU

The reason for not using atomic units is that should V be assigned an expression or number, then the variable is no longer R[V] but R[what ever V is defined]. For example;

Download MaplePrimes_subscripts.mw

However, the notification flag is still a hit or miss at loading. 

Does the notification flag work for you? I click on it, and the circling star image never shows anything useful anymore. It just keeps saying "Loading."  Maybe it is just me. 

(I like the flag idea. I used to work.)

@Scot Gould that post required nearly a minute to be uploaded.

Sometimes it requires multiple temps to load a page. I'm glad to find out that I'm not the only person who is observing this behavior.

@acer Apparently, the ability to control the position of a graph in the Array is not a high priority. At least this post was relatively easy to locate in MaplePrimes. Thanks for the recommendation. 

@FDS Even if one uses 2d-input, at the execution group command line, set the input as "text." (See the box at the top of the window.) Then paste.  It works. 

(I too prefer 2d math input.) 

Hopping on to what @Carl Love contributed and assuming I understand what is going on here, I prefer not to extend the arrow over the subscript.  Refer to the blue version of the vector label.

T := Typesetting;
plots:-display(
  plots:-textplot([1, 2, T:-mover(T:-msub(T:-mi("abc"), T:-mn("def")), T:-mo("→")),  color = red], 
                          font = [arial, bold, 16]), 
  plots:-textplot([2, 2, T:-msub(T:-mover(T:-mi("abc"), T:-mo("→")), T:-mn("def")), color = blue], 
                          font = [arial, bold, 16]), 
  axes = none);

@WD0HHU I don't see an uploaded version. If you reply to this post with the .mw file, I'll look at it. But it sounds like your best bet is to increase your zoom factor while making the graph smaller. 

@WD0HHU Hmm, I'm not entirely sure what symbol fonts you want to enlarge. So, let me make two suggestions instead.

1) Make the graphs smaller. 

Just after the restart command, add the line:

  plots:-setoptions( size = [350, 350] )

(I have added this line to the initialization file so that all my graphs are smaller.)

2) Set the Zoom Factor to 125% or 150%. 

Now re-execute the worksheet, and you will see the fonts are larger compared to the graph size. 

I also recommend looking at other examples of Explore. In HELP, look for 'examples, Explore'. 

@C_R I agree the two solutions work. And we agree p__1 is not the same as p__2. Hence, is(p__1 = p__2) should return a false, which it does in some versions. 

@Kitonum 

Download Exponential_rule.mw

@Carl Love Yes,  solve did not choke. Given how I had written the solve expression,  I misread the eval error statement. (It is humongous, as one can expect.)  Specifically, I copied the OP line  solve({equations}, [seq of variables]) rather than solve({equations}, {variables})  eval(s, T[1]) produced a result.  

Unless I mistyped the problem, even though I declared gamma to be local, the output is too complicated that Maple does not execute. Solving the set of non-linear equations without an output

  T:= solve({f1, f2, f3, f4, f5, f6}, [s, v, e, i, q, r]):

for the unknowns and asking for the expression of s

eval(s, T)

produced and "invalid input." Hence, no solution was returned.

Please, next time use the big green arrow to upload your worksheet.

@sursumCorda In Maple, variables are altered based on when a command is executed. In Flow, variables are altered based on where the command exists in the worksheet. 

Based on my experience teaching new users for a dozen years or so, getting these folks to recognize that if they correct a line in the middle of the calculations, it does not mean the line at the end of the calculation is immediately corrected. The new users will say to me, "My worksheet does not work even though it looks like it should work because the commands are laid out in the correct sequence." I often "fix" their error by going back to the restart command and hitting <Enter><Enter><Enter> several times. (I recommend worksheet mode over document mode for new users.)

In Flow, it is what you see is what you get. If you correct a previous line, all subsequent lines are updated and corrected. This is why when if first attempted to introduce computation into my physics courses, I started with Mathcad. However, I found Maple to be a more robust CAS, so I switched to it.