Greetings

Overview

• starmapper-core: a class/interface library; it performs lots of CPU-heavy calculations given so-called reports and returns a BufferedImage∞. This can be a one-time operation or a batch. Batch mode means that you give it a bunch of reports to read from and in return you get a BlockingQueue∞ that will be populated with results over time;
• starmapper-app-cli: a traditional CLI application;
• starmapper-app-gui: an additional GUI application for non-geeks [actually it's "traditional" too, in a sense that it was available since Starmapper version 1, but it has always been a second-class citizen ;)];
• jezuch-utils: a library of support classes that are generic (pun intended, for those that get the joke) enough to put them in a library separate from Starmapper.

Concepts

• The Map™: a two-dimensional region. "Two-dimensional" means that every point can be reached by giving two coordinates; currently the coordinates are integer numbers (so the precision is limited, but sufficient for all uses known to me - if you need more, gotta ping me). Important component of The Map is The Space. It is uniformly flat - so forget about mapping a reachability of electromagnetic waves in a complex terrain (sorry);
• Nodes: points on the The Map. They are the basic "skeleton" on which Starmapper operates. They can't move [patches welcome ;)], they have some properties - like position and name - and can belong to at most one region (can also be owned by noone);
• Regions: these are a virtual beings that reside on nodes and can "reach" through a space to claim "ownership" of it. Each node can have at most one owning region; it is then determined what "influence" this node has on the surrounding space. The result is a field (as in physics∞) of influences for each region on the map. At the end, a thing called Plotter takes this data and creates a pretty picture∞.
• Node Infos: basically a set of data describing a node at a point in time. Time is specified in unspecified units (which makes some awkward wording in the code - it's just "time" everywhere). Data about a node can contain anything is necessary to calculate its influence, but Starmapper is interested only in the result, including the influence, who is the owner and who says these things about the node (that is reporter);
• Reports: report is simply a collection of Node Infos from one point in time. There can be more reports from the same time, provoded that they have different reporters (reporter is one of the regions on The Map). Every Node Info in a report has an age (how fresh it is). In case of conflicts between Node Infos in two reports about the same node, report age becomes important as the final report can't have multiple sets of information about each node - they have to be merged. Merging is a responsibility of Data Model (see below);
• Data Model: since version 3, nodes, regions and node infos are all actually Java interfaces - this makes Starmapper somewhat generic tool, and the outside world needs to provide concrete implementations of these interfaces. Starmapper bundle contains a default set of implementations that represent galaxies in Stars! game [that's how Starmapper started - I used to be a Stars! junkie].
• Unified Configuration Model: this buzzword-sounding name means a system of passing somewhat type-safe parameters to Starmapper. The same infrastructure can be used by client applications, of course, and that's why it's called "unified".

Historical Note

• SourceForge.net page: http://sourceforge.net/projects/starmapper∞
  
  
  Deletions:
  - Sample images: from version 2∞; previews from upcoming version 3 (the same map, different plotters): CappedPlotter∞, CappedPlotter with a bug ;)∞, SmoothPlotter∞, MixingPlotter∞
  
  
  

  ---

  
  Edited on 2006-09-08 11:41:53 by KrzysztofSobolewski
  
  Additions:
  - Version 3: progressed from somewhere between alpha and beta (I like to call it gamma) to more-or-less stable API and solidly working implementation; no releases yet, code is in SVN∞;
• starmapper-core: a class/interface library; it performs lots of CPU-heavy calculations given so-called reports and returns a BufferedImage∞. This can be a one-time operation or a batch. Batch mode means that you give it a bunch of reports to read from and in return you get a BlockingQueue∞ that will be populated with results over time;
  
  Deletions:
  - Version 3: somewhere between alpha and beta (I like to call it gamma); no releases yet, code is in SVN∞;
• starmapper-core: a class/interface library; it performs lots of CPU-heavy calculations given so-called reports and returns a BufferedImage∞. This can be a one-time operation or a batch. Batch operation means that you give it a bunch of reports to read from and in return you get a BlockingQueue∞ that will be populated with results over time;
  
  

  ---

  
  Edited on 2006-09-08 11:24:49 by KrzysztofSobolewski
  
  Additions:
  - starmapper-core: a class/interface library; it performs lots of CPU-heavy calculations given so-called reports and returns a BufferedImage∞. This can be a one-time operation or a batch. Batch operation means that you give it a bunch of reports to read from and in return you get a BlockingQueue∞ that will be populated with results over time;
  
  Deletions:
  - starmapper-core: a class/interface library; it performs lots of CPU-heavy calculations given so-called reports and returns a BufferedImage∞ [NOTE: this is a traditional Starmapper's mode of operation which places lots of burden on client application which needs to find all data files, use starmapper-core to read them and feed the results back to starmapper-core; this may change in version 3];
  
  

  ---

  
  Edited on 2006-08-30 05:22:46 by KrzysztofSobolewski
  
  Additions:
  - Unified Configuration Model: this buzzword-sounding name means a system of passing somewhat type-safe parameters to Starmapper. The same infrastructure can be used by client applications, of course, and that's why it's called "unified".
  
  

  ---

  
  Edited on 2006-08-16 05:45:22 by KrzysztofSobolewski [Too many Nodes, I think...]
  
  Additions:
  

  Historical Note

  
  
  Deletions:
  

  Historical Node

  
  
  

  ---

  
  Edited on 2006-08-15 14:02:58 by KrzysztofSobolewski
  
  Additions:
  - Node Infos: basically a set of data describing a node at a point in time. Time is specified in unspecified units (which makes some awkward wording in the code - it's just "time" everywhere). Data about a node can contain anything is necessary to calculate its influence, but Starmapper is interested only in the result, including the influence, who is the owner and who says these things about the node (that is reporter);
  
  Deletions:
  - Node Infos: basically a set of data describing a node at a point in time. Time is specified in years, currently [that's a leftover from previous versions, didn't know how to rename it; see "historical note" below]. Data about a node can contain anything is necessary to calculate its influence, but Starmapper is interested only in the result, including the influence, who is the owner and who says these things about the node (that is reporter);
  
  

  ---

  
  Edited on 2006-08-15 08:48:52 by KrzysztofSobolewski
  
  Additions:
  - Sample images: from version 2∞; previews from upcoming version 3 (the same map, different plotters): CappedPlotter∞, CappedPlotter with a bug ;)∞, SmoothPlotter∞, MixingPlotter∞

• Version 2: StarmapperLib 2.3.4∞, StarmapperApp 2.2.3∞, StarmapperGUIApp 2.5.1∞; all released 2005-06-12;
• Version 1: Starmapper 1.21∞, released 2002-05-05 (from before the split into three).
• Full Disclosure: old starmapper page∞ (but... be... prepared...)
• Sample image: from version 2∞
• The Map™: a two-dimensional region. "Two-dimensional" means that every point can be reached by giving two coordinates; currently the coordinates are integer numbers (so the precision is limited, but sufficient for all uses known to me - if you need more, gotta ping me). Important component of The Map is The Space. It is uniformly flat - so forget about mapping a reachability of electromagnetic waves in a complex terrain (sorry);
• Nodes: points on the The Map. They are the basic "skeleton" on which Starmapper operates. They can't move [patches welcome ;)], they have some properties - like position and name - and can belong to at most one region (can also be owned by noone);
• Regions: these are a virtual beings that reside on nodes and can "reach" through a space to claim "ownership" of it. Each node can have at most one owning region; it is then determined what "influence" this node has on the surrounding space. The result is a field (as in physics∞) of influences for each region on the map. At the end, a thing called Plotter takes this data and creates a pretty picture∞.
• Node Infos: basically a set of data describing a node at a point in time. Time is specified in years, currently [that's a leftover from previous versions, didn't know how to rename it; see "historical note" below]. Data about a node can contain anything is necessary to calculate its influence, but Starmapper is interested only in the result, including the influence, who is the owner and who says these things about the node (that is reporter);
• Reports: report is simply a collection of Node Infos from one point in time. There can be more reports from the same time, provoded that they have different reporters (reporter is one of the regions on The Map). Every Node Info in a report has an age (how fresh it is). In case of conflicts between Node Infos in two reports about the same node, report age becomes important as the final report can't have multiple sets of information about each node - they have to be merged. Merging is a responsibility of Data Model (see below);
• Data Model: since version 3, nodes, regions and node infos are all actually Java interfaces - this makes Starmapper somewhat generic tool, and the outside world needs to provide concrete implementations of these interfaces. Starmapper bundle contains a default set of implementations that represent galaxies in Stars! game [that's how Starmapper started - I used to be a Stars! junkie].
  
  Deletions:
  - Version 3: somewhere between alpha and beta (I like to call it gamma); no releases yet, code is in SVN;
• Version 2: StarmapperLib 2.3.4∞, StarmapperApp 2.2.3∞, StarmapperGUIApp 2.5.1∞; all released 2005-06-12;
• Version 1: Starmapper 1.21∞, released 2002-05-05 (from before the split into three).
• The Map™: a two-dimensional region. "Two-dimensional" means that every point can be reached by giving two coordinates; currently the coordinates are integer numbers (so the precision is limited, but sufficient for all uses known to me - if you need more, gotta ping me). Important component of The Map is The Space. It is uniformly flat - so forget about mapping a reachability of electromagnetic waves in a complex terrain (sorry);
• Nodes: points on the The Map. They are the basic "skeleton" on which Starmapper operates. They can't move [patches welcome ;)], they have some properties - like position and name - and can belong to at most one region (can also be owned by noone);
• Regions: these are a virtual beings that reside on nodes and can "reach" through a space to claim "ownership" of it. Each node can have at most one owning region; it is then determined what "influence" this node has on the surrounding space. The result is a field (as in physics∞) of influences for each region on the map. At the end, a thing called Plotter takes this data and creates a pretty picture∞.
• Node Infos: basically a set of data describing a node at a point in time. Time is specified in years, currently [that's a leftover from previous versions, didn't know how to rename it; see "historical note" below]. Data about a node can contain anything is necessary to calculate its influence, but Starmapper is interested only in the result, including the influence, who is the owner and who says these things about the node (that is reporter);
• Reports: report is simply a collection of Node Infos from one point in time. There can be more reports from the same time, provoded that they have different reporters (reporter is one of the regions on The Map). Every Node Info in a report has an age (how fresh it is). In case of conflicts between Node Infos in two reports about the same node, report age becomes important as the final report can't have multiple sets of information about each node - they have to be merged. Merging is a responsibility of Data Model (see below);
• Data Model: since version 3, nodes, regions and node infos are all actually Java interfaces - this makes Starmapper somewhat generic tool, and the outside world needs to provide concrete implementations of these interfaces. Starmapper bundle contains a default set of implementations that represent galaxies in Stars! game [that's how Starmapper started - I used to be a Stars! junkie].
  
  

  ---

  
  Oldest known version of this page was edited on 2006-08-14 12:52:04 by KrzysztofSobolewski []
  
  Page view:

  Status

• Version 3: somewhere between alpha and beta (I like to call it gamma); no releases yet, code is in SVN;
• Version 2: StarmapperLib 2.3.4∞, StarmapperApp 2.2.3∞, StarmapperGUIApp 2.5.1∞; all released 2005-06-12;
• Version 1: Starmapper 1.21∞, released 2002-05-05 (from before the split into three).

Greetings

Overview

• starmapper-core: a class/interface library; it performs lots of CPU-heavy calculations given so-called reports and returns a BufferedImage∞ [NOTE: this is a traditional Starmapper's mode of operation which places lots of burden on client application which needs to find all data files, use starmapper-core to read them and feed the results back to starmapper-core; this may change in version 3];
• starmapper-app-cli: a traditional CLI application;
• starmapper-app-gui: an additional GUI application for non-geeks [actually it's "traditional" too, in a sense that it was available since Starmapper version 1, but it has always been a second-class citizen ;)];
• jezuch-utils: a library of support classes that are generic (pun intended, for those that get the joke) enough to put them in a library separate from Starmapper.

Concepts

• The Map™: a two-dimensional region. "Two-dimensional" means that every point can be reached by giving two coordinates; currently the coordinates are integer numbers (so the precision is limited, but sufficient for all uses known to me - if you need more, gotta ping me). Important component of The Map is The Space. It is uniformly flat - so forget about mapping a reachability of electromagnetic waves in a complex terrain (sorry);
• Nodes: points on the The Map. They are the basic "skeleton" on which Starmapper operates. They can't move [patches welcome ;)], they have some properties - like position and name - and can belong to at most one region (can also be owned by noone);
• Regions: these are a virtual beings that reside on nodes and can "reach" through a space to claim "ownership" of it. Each node can have at most one owning region; it is then determined what "influence" this node has on the surrounding space. The result is a field (as in physics∞) of influences for each region on the map. At the end, a thing called Plotter takes this data and creates a pretty picture∞.
• Node Infos: basically a set of data describing a node at a point in time. Time is specified in years, currently [that's a leftover from previous versions, didn't know how to rename it; see "historical note" below]. Data about a node can contain anything is necessary to calculate its influence, but Starmapper is interested only in the result, including the influence, who is the owner and who says these things about the node (that is reporter);
• Reports: report is simply a collection of Node Infos from one point in time. There can be more reports from the same time, provoded that they have different reporters (reporter is one of the regions on The Map). Every Node Info in a report has an age (how fresh it is). In case of conflicts between Node Infos in two reports about the same node, report age becomes important as the final report can't have multiple sets of information about each node - they have to be merged. Merging is a responsibility of Data Model (see below);
• Data Model: since version 3, nodes, regions and node infos are all actually Java interfaces - this makes Starmapper somewhat generic tool, and the outside world needs to provide concrete implementations of these interfaces. Starmapper bundle contains a default set of implementations that represent galaxies in Stars! game [that's how Starmapper started - I used to be a Stars! junkie].

Historical Node

Page History :: 2007-11-28 08:36:40 :: Owner: KrzysztofSobolewski :: Search: