|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||
java.lang.Objectorg.xistrat.util.ExportData
org.xistrat.util.ExportOrbits
org.xistrat.util.ExportVector
public class ExportVector
dump group data
| Field Summary |
|---|
| Fields inherited from class org.xistrat.util.ExportData |
|---|
_vertices, _verts, faceData, fastFace, poly, polygons |
| Constructor Summary | |
|---|---|
ExportVector(java.lang.String graph,
java.lang.String old_variant,
java.lang.String outfile,
int mode,
int s,
java.util.LinkedList<FigurData> pieces)
|
|
| Method Summary | |
|---|---|
void |
resetSwitches()
some quite simple 'naive probabilistic doubling procedure' variant 'color' all vertices in a randomized way, (that is to say specify the switches for the dual_rot), then undo where collisions occur, and finally finish with some greedy setting another option is backtracking (and of course we hope that a deterministic procedure will be possible later on) (and yes, actually now we have the -q -s 4 instead for the cover stuff) if ok then a desired outcome has been found or not |
| Methods inherited from class org.xistrat.util.ExportOrbits |
|---|
doMultiBodySP, doSP, fillMultiBodyTrails, fillTrails, fillTrails, fillTrails, fillTrails, fillTrails, getAddon, getAxis, getAxis, getAxis, getDistIE, getDistIE, getMultiBodyAxis, getMultiBodyAxis, getSummand, isOrig, moveEndToFront, moveFrontToEnd |
| Methods inherited from class org.xistrat.util.ExportData |
|---|
main |
| Methods inherited from class java.lang.Object |
|---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Constructor Detail |
|---|
public ExportVector(java.lang.String graph,
java.lang.String old_variant,
java.lang.String outfile,
int mode,
int s,
java.util.LinkedList<FigurData> pieces)
graph - surface to be usedold_variant - optionally what variantoutfile - where to direct the outputmode - what sort of group to be createds - for the default option (rot/flip group) specify if
0:'double',
1:fixing labels toward holes during flip,
2:holes as valid is chosen,
3:some unofficial tryings (using switches),
4: or that simultaneously ordered pairs of points plus ordered pairs of faces shall map to the labels used ('connected-over-multiple-edges', vertices connected over one single edge, and edge-loop graphs)
in case of the -q mode the s param has different meanings, see below
| Method Detail |
|---|
public void resetSwitches()
throws java.io.IOException
'color' all vertices in a randomized way, (that is to say specify the switches for the dual_rot), then undo where collisions occur, and finally finish with some greedy setting
another option is backtracking (and of course we hope that a deterministic procedure will be possible later on) (and yes, actually now we have the -q -s 4 instead for the cover stuff) if ok then a desired outcome has been found or not
java.io.IOException
|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||