Exercises, prim_old via search

Author: lee-naish

src/algorithms/extra-info/QSInfo.md

@@ -22,6 +22,11 @@ Geeks for Geeks Link: [**Quicksort**][G4GLink]
 
 ## Exercises/Exploration
 
+The AIA progress bar allows you to see how many steps there are in the
+animation, which is a *very rough* guide to run-time. Plot the
+number of steps versus the number of data items, for sorted data - what
+does it show?
+
 Look into some of the history of quicksort.  The basic idea is relatively
 simple and was invented long ago. However, it has had a *huge* amount
 of work done on it over the years to refine it in many ways - far more

src/algorithms/extra-info/StraightRadixSortInfo.md

@@ -28,6 +28,16 @@ In *counting sort*, temporary array **B** is filled by scanning array
 **B** would still end up sorted on the digit in question.  What would
 the affect be on the radix sorting if left to right scanning was used?
 
+How is the run-time of Straight Radix Sort affected by the order of the
+data?
+
+The AIA progress bar allows you to see how many steps there are in the
+animation, which is a *very rough* guide to run-time. By experimenting
+with different input data, can you devise a formula for how many steps
+there are, given the number of data items and the number of (base 4)
+digits?
+
 Look up how sorting punched cards has been done historically. Card
 sorting machines used LSD radix sorting! How could you sort a deck of
 playing cards using LSD radix sorting?
+

src/algorithms/index.js

@@ -21,13 +21,19 @@ import * as Instructions from './instructions';
  algorithm is deployed. Note that the DEFAULT_ALGORITHM from
  src/context/actions.js had better be deployed!
  XXX Design of noDeploy stuff was done with the aim of minimal code change
- and could be re-thought when there are fewer merges going on.
+ and should be re-thought when there are fewer merges going on.
 XXX This has now been totally ****ed up, with multiple lists of
 algorithms elsewhere (see components/mainmenu/index.js
-components/mainmenu/GraphAlgorithms.js components/AlgorithmMenu.js) as
+components/mainmenu/GraphAlgorithms.js etc components/AlgorithmMenu.js) as
 well as this file, algorithms/index.js. There should be *one* master
 list (eg, this one, possibly with extra info for each algorithm) and the
 other lists should be generated from the master list!
+Currently with noDeploy=true the algorithm can still be found via the
+search function but it then says "Invalid algorithm specified" - see
+algorithms/parameters/helpers/urlHelpers.js (XXX that file could use
+allalgs instead??)
+Now that we can access algorithms via the URL we should be able to use
+this mechanism for acess to "hidden" algorithms
 
  Each imported algorithm is expected to be an object of the form:
  { pseudocode: String, explanation: String, run: Function }
@@ -372,7 +378,7 @@ const allalgs = {
   // Prim's (simpler code) is superseeded + could do with some work;
   // it's included here so it can be run but it's not included in menus
   'prim_old': {
-    noDeploy: true,
+    // noDeploy: true,
     name: 'Prim\'s (simpler code)',
     category: 'Graph',
     explanation: Explanation.Prims_oldExp,