Tips

A)
A monophonic line can be made polyphonic by replacing a '[', ']' pair with '{', '}'. Or you can just surround a section of a rule replacement with '\', and  '/'.

B)
Set numerical parameters in the axiom or replacements using declared constants rather than in the rules. For example:
	c(12)F
could be replaced by setting:
	i1=12
in the Declare Box and using:
	c(i1)F
in the replacement. The reason for doing it this way is that the constant name (i1) is not converted to a number until interpretation so you can change the instrument/color in the declare box (set i1=47, for example) and re-interpret, rather than having to 'make' the production string again.

C)
Make a map file containing commonly used constants, scales, etc. (see lmuse.html on creating a map file). This file can be loaded using 
	File->Load Map File
at any time independent from other map file you may be using (That is, the values in your 'utility map file' will only be added to what is already loaded). See, for an example, the file 'scales.ini' in the Examples directory. If the file contains nothing but scales, like 'scales.ini', make the first line of the file 'nomap'. This ensures that the scales won't be automatically assigned to a map (a kludgy fix for the fact that 'scale' is used both to define a scale and assign a scale)

D)
You will notice that when declaring constants with a formula, like "phi=(sqrt(5)-1)/2", they are immediately converted to numerical values and when the rules or rule w/ map file is saved, the constant name is associated with the numerical value rather with than the formula. For example, "phi=(sqrt(5)-1)/2" ends up being saved as "phi=0.6180339887498949". 