I write a script like Java interface to handle the option settings.
Try to keep the same options and values on the http://sparse.tamu.edu
I am not sure whether it is suitable in the ssget script.
the following is copied from build_from_config.md
BuildFromConfig
It try to allow the same options as the filters on
(sparse.tamu.edu).
Usage
./build_from_config.sh configfile
The output is the searching command. ./ssget -s 'output'
In configfile, it allows use the // to mark the comments
OPT_NAME:VAL for setting the option value
I write a script like Java interface to handle the option settings. Try to keep the same options and values on the http://sparse.tamu.edu I am not sure whether it is suitable in the ssget script.
the following is copied from
build_from_config.md
BuildFromConfig
It try to allow the same options as the filters on (sparse.tamu.edu).
Usage
./build_from_config.sh configfile
The output is the searching command.
./ssget -s 'output'
In
configfile
, it allows use the//
to mark the commentsOPT_NAME:VAL
for setting the option valueNo
meansNot_Implement
NO
|Strongly Connected ComponentsNO
|IntegerNO
|Skew-SymmetricNO
|Matrix IDNO
|YearDetail
For the
OPT:min,max
, it allows onlymin
ormax
with keeping,
OPT:,max
means the conditionOPT<=max
For the
OPT:OPTION
, it only allows one option now.Difference from (sparse.tamu.edu)
kind
,groupname
,matrixname
contain thekeyword
(it is case insensitive)Example
example in ssget:
400 <= #rows <= 450 and numerical symmertry >= 0.99
the output of
./build_from_config config
is[ @rows -ge 400 ] && [ @rows -le 450 ] && [ $(echo "@nsym <= 0.99" | bc) -eq 1 ]
output is
[ @rows -ge 200 ] && [ @cols -le 300 ] && [ @nonzeros -ge 1000 ] && [[ @real == true ]] && [[ @rows == @cols ]] && [[ @nsym == 1 ]] && [[ @posdef == true ]]