Posts

Post marked as solved
2 Replies
0 Views
I re-tested on the 4x4 example given in Apple documentation on Creating a Sparse Matrix from Coordinate Format Arrays. Adjusted all the coordinates up by 1 and ran with the code with the - 1 to reduce the coordinate rows and columns coordinates just to be sure. Everything works (answers are correct). So, I just have to remember when downloading to check the coordinates to see where they start, and adjust if need be.
Post marked as solved
2 Replies
0 Views
I am more than dumb ... but may I be excused for being such an amateur? Not! Haha. So, I thought I could use the Ldoor matrix directly after stripping off the headers. That part I got right. But I failed to realize in order to use the SparseConvertFromCoordinate I was required to adjust the coordinate format row and column number from 1, 1 to 0, 0 , and, of course, for all subsequent coordinate format rows and columns. I updated the original code with this part of code which reduces coordinate numbers by 1. And everything ran! Well, at least I got some answers and exit code 0. // assign forced unwrapping for casting to appropriate arrays for index in 0...rowcountm1 { rows32[index] = Int32(rows![index] - 1 ) cols32[index] = Int32(cols![index] - 1 ) datsdouble[index] = Double(dats![index]) }
Post marked as solved
5 Replies
0 Views
Replied In Float16 use
Would Float16 work on an M1 Mac computer?
Post marked as solved
5 Replies
0 Views
Replied In Float16 use
Thank you. Understood. And the tvOS also works! ... I just didn't wait until playground had done its thing. I guess I really should have a static ram drive!
Post marked as solved
5 Replies
0 Views
Replied In Float16 use
Thank you, eskimo! I just found that was the case ... and was going to reply to my own problem! I didn't read, or see the scope restrictions. I know it may be obvious, but I got confused after watching the Swift 5.3 video. Would you know if it will be made available for the Macs? Also, tvOS? Thank you, again.
Post not yet marked as solved
36 Replies
0 Views
My Cholesky decomposition issue has been addressed with the Mojave macOS (Apple said that it would be fixed with Mojave). When I went to clear the bug report that I had originally filed I couldn't find the bug report in Bug Reporter. So I am just reporting that the issue has been cleared here.