Replies: 1 comment
-
@yangbo116, I have made some very minor changes to The problem was a combination of both the conventions (which the original author had intended for the use of It will take me a little longer to create a new release as I have some more critical things planned for that (including removal of calls to the |
Beta Was this translation helpful? Give feedback.
-
I use the SDPA python (https://sdpa-python.github.io/docs/usage/) version to generate a SDPA format as the Sparse Input Data File in user Manual, but I get the follow format:
3
1
2S
-4.8000000000000000e+01 +8.0000000000000000e+00 -2.0000000000000000e+01
0 1 1 1 +1.1000000000000000e+01
0 1 2 2 -2.3000000000000000e+01
1 1 1 1 -1.0000000000000000e+01
1 1 1 2 -4.0000000000000000e+00
2 1 2 2 -4.0000000000000000e+00
3 1 1 2 +8.0000000000000000e+00
3 1 2 2 +2.0000000000000000e+00
, which is not consistent with the results in user Manual:
"Example 1: mDim = 3, nBLOCK = 1, {2}"
3 = mDIM
1 = nBLOCK
2 = bLOCKsTRUCT
{48, -8, 20}
0 1 1 1 -11
0 1 2 2 23
1 1 1 1 10
1 1 1 2 4
2 1 2 2 -8
3 1 1 2 -8
3 1 2 2 -2
, at the m=2, 1 block, (2, 2): value -8, but in python,this position is -4. So, is anything wrong in python code?
Beta Was this translation helpful? Give feedback.
All reactions