Using the package seems fine to me. The Python code uses a package. We’re using packages in the code for the other chapters, too.
For all the people working on chapters, there has been some discussion of whether to put code inside functions, as is usual for Julia, or to leave code in the global scope, using the same style as the Python and Matlab code. For now, let’s leave the code pieces unwrapped, ok? Assume that the code pieces can be pasted into a newly started REPL which has all dependencies available. Or, executed from VS Code using CTRL-enter.
1 Like
This effort is nearing completion. Before we notify the book’s author that it’s ready to use, if would be nice to receive any reports about errors or other problems. Please give it a try, if you’re interested, and raise an issue if you find a problem. https://github.com/mcreel/IntProbDS.jl
5 Likes
Stanley Chan said “What an amazing speed!!!” when I informed him that the translations were done. :juliabouncing: :juliabouncing: :juliabouncing: I have asked him to link to contributors section of the github page to credit the people who have contributed, and he will do so.
13 Likes
And that using global contributors. If they were in a local scope it would have taken a minute. Congratulations!
10 Likes
Hmm, I see. I think that the author is changing the unicode to plain text himself, but he’s not finished yet. Let’s wait a few days and see if it gets fixed that way.
1 Like
I’m checking that this is all working correctly still with Julia 1.9.x and updated packages. It appears to me that
Ch07 @Paul_Soderlind
Ch08 @mcreel 
Ch09 @mcreel
Ch10 @congUoM
all have minor issues.
I can have a look at them, but maybe the original contributors would like to go first?
edit: chs 08 and 09 are done, it was very minor stuff. I have added some "##"s here and there to allow easy code block execution when using VSCode.
The working branch of the archive is GitHub - mcreel/IntProbDS.jl at update
5 Likes
Question: are we aiming for minimal changes or “good” changes?
Reason for asking: Ch07 uses Convex.jl, which is not actively developed. Personally, I now use OSQP.jl for these sort of things.
I could thus either stick with Convex.jl and do minimal changes or port it to OSQP. Any preferences?
Hi, Paul. The code on GitHub is yours, without modification (as far as I recall). A PR against that would be good, or email, or whatever is convenient.
Regarding OSQP, that sounds like a good idea to me. There’s no particular reason why the code can’t change. Best, M