CMOD
tracer 2.0 experimental service pack 1.0
Why an experimental service pack?
Facing with the problems of this map:
http://www.shatters.net/forum/viewtopic.php?f=5&t=16045in which the same geo-age's text must have different Importance directive, I've made few modification to the CMODtracer.
1) Completely rebuilt the "mylocs.pl" script in order to assign also the Importance;
2) Added one function to the "cmod_tracer.lua" in which is taken into account the linear assignment of the custom Importance(s) through the relation (observer/object)-radius.
Enstabilished the superior/inferior limits for the distances and its Importance's values, all the remains values are within this range. For my geomap's purpose I use 5 linear values, but they could be morer, both randomized and not linear as well. In sumn, in my case they depend on the linear "zoom in".
Now, when CMODtracer does pick up a coordinate, it add also the relevant, computed, Importance. In this manner the file "coordinates.txt" has 3 values: lat/long/importance respectively. Note that the addition of further values inside the "coordinates.txt" doesn't change the way in which the Perl constructors deal with the CMODs, since the
split function wasn't set to reckon it. One can continue to use the CMODtracer as usual. It's just in the case of "coordinate's picking" which they assumes relevance.
Once the "coordinates.txt" is full of points and Importance(s), the new "mylocs.pl" is able to process them by assigning only one name for the several Importance(s). In this way the same geo-name has just high Importance's value for big areas and just low Importance for small areas of the map. This procedure can be improved either with a further Lua textbox in which to display the Importance itself, or with a PNG centered on screen and made like a submarine's periscope.
Note that if to the Perl
split function is assigned also the third value, it should be the Z value whether in the Lua module is disabled the Importance's computation and is left instead just the distance. Centered on an object, one could make 3D objects when tasselated. A discussion about the triangle tasselation of XYZ dataset is here:
http://forum.celestialmatters.org/viewtopic.php?t=337However, 2 screenshots of the new "mylocs.pl" script.
![Image](http://marauder.webng.com/images/mylocs_1.jpg)
The front-end, the help.
![Image](http://marauder.webng.com/images/mylocs_2.jpg)
The Menu Options.
The options should be pretty selfexplanatories; Option 4 is the option which perform the discourse above.
The default Importance is customizable in the first part of the script, in which there are the location's directives.
Option 2, together with the manual name, it assign also the manual Importance.
With the option rename one can save with another name the "mylocs.ssc" for making another (in the same time the original will be cleaned up.
The script avoid the double entering of the precedent versions and is less error prone. The options can be interactives. Now the letter "#" is used to return to the menu in whichever step.
Importance values and distances are easy individuables in first part of "cmod_tracer.lua" and the function as well.
Being experimental, one could to add its distance/Importance parameters in more quantity; if more values are added, let's add also the relevant conditionals to the function.
For Windows users the "mylocs.pl" is shipped also as batch file. For making batch files of the Perl scripts
type within the Win cmd: pl2bat "yourfile.pl" "yourfile.bat" (without quotes) then enter
Zip:
http://marauder.webng.com/files/cmod_tracer_2.0_sp1.zip (8kb)
3 files: "cmod_tracer.lua", "mylocs.pl", "mylocs.bat". Backup the previous, first.
Never at rest.
Massimo