Module sdjas :: Class SD_Ideal

Class SD_Ideal

This class represents a SymbolicData database object. The constructor takes a complete URI or a name SUBJ (the latter of which will be prefixed with the 'ideal' value from the sd.ini)

Any triple of the form (SUBJ, PRED, OBJ) will yield a field PRED* for the SD_Ideal object with the value OBJ, where PRED* is the ending piece of PRED URI as defined by the function _uri_to_name()

A SPARQL endpoint is needed. As a future improvement, it could be nice to directly parse an RDF in a convienient serialization.

Instance Methods

[hide private]

__init__(self, sd, name)
sd is a SymbolicData object, the name can be a complete URI or shortened name as defined by _uri_to_name().

source code

get_ideal(self)
Return the ideal as a Jas objects.

source code

__addXMLResource(self, link)

source code

__constructJasObject(self)

source code

jas_hasLengthsList(self)
This is the implementation of the predicate "sd:hasLengthsList".

source code

jas_hasDegreeList(self)
This is the implementation of the predicate "sd:hasDegreeList".

source code

jas_hasVariables(self)
This is the implementation of the predicate "sd:hasVariables".

source code

jas_homogenize(self, hv)
Homogenize a basis, which here means actually nothing more than homogenizing every element of the basis.

source code

Method Details

[hide private]

init(self, sd, name)
(Constructor)

source code

sd is a SymbolicData object, the name can be a complete URI or shortened name as defined by _uri_to_name(). The latter will be prefixed with the 'ideal' value from the sd.ini. Namespaces like "sd:Wu-90" are not (yet) supported.

Appart from retrieving the information from the SPARQL endpoint, the resource data (XML files) is needed as well. While the SPARQL endpoint can be substituted by another SPARQL endpoint, the links to the resource files are 'hard-coded' into the RDF data. The possibility to use a (possibly 'hand-filled') cache will be included in the next update.

jas_hasLengthsList(self)

source code

This is the implementation of the predicate "sd:hasLengthsList". The lengths lists is the sorted list of the number of monomials of the generator of the ideal.

Along with the output, there will also be generated a field FROM_JAS_hasLengthsList which can be used to later access the data without recalculating. The main reason for this is that the SymbolicData properties are converted into field, not getter functions. So to have some symmetry, the Jas calculations will end up in fields as well.

jas_hasDegreeList(self)

source code

This is the implementation of the predicate "sd:hasDegreeList". The degree list is the sorted list of the degree of the generator of the ideal.

Along with the output, there will also be generated a field FROM_JAS_hasDegreeList which can be used to later access the data without recalculating. The main reason for this is that the SymbolicData properties are converted into field, not getter functions. So to have some symmetry, the Jas calculations will end up in fields as well.

jas_hasVariables(self)

source code

This is the implementation of the predicate "sd:hasVariables". This is actually not needed.

Class SD_Ideal

__init__(self, sd, name) (Constructor)

jas_hasLengthsList(self)

jas_hasDegreeList(self)

jas_hasVariables(self)

init(self, sd, name)
(Constructor)