For slotted HE, the shield will be Mumetal, as per URL, does not take kindly to being welded as i saw on one photo.
www.magnetic-shield.com
Yes digital ignitions work on retard only, for iis this was 40dbtdc, if you wanted a 25dbtdc ignition point vector, it will be 40-25 equal 15 degrees retard from 40degrees forward reference.
Points are no different with a centrifugal moving weight system, at full inertial force the points are at maximum Xdbtdc usually 32, as the revs reduce the inertia reduces and the points are counting back from 32 degrees. 32dbtdc is the forward reference. Takes a bit of getting used to "retard" when all you were told "advance" is how it works, you cannot have advance, as your indicating an event in the future, from an event that has not happened, its absurd.
Example, say you have 3 degrees of retarded spark event, from a forward reference at maximum, you then try to advance the retarded spark event by 3 degree, your already at maximum forward reference vector, how can you go past the forward reference? You cannot, that easy. If you were at say 10degrees after forward reference vector, the you could fudge the new spark event by 10-3 ( not 10+3 ) its a negative event when using forward reference vector. That would map, if your ignition control was offering that facility, does it then increase all ignition events down to idle? If so you would then have percentage errors, 3degrees at base idle of say 9degrees would be a 33% error... leave ignitech to support their product, as to what some here are attempting.
In conclusion, no matter what you do to a digital map, if your crank to crank encoder has an inherent error offset, then you may reduce the error up to the forward reference vector, you cannot go past that reference vector, however. All care to make this as transparent as a sheet of glass, you see?... a wry smile here. j