-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added callout box linking to Octave #38
Conversation
This is just a draft but I think it would be nice to reference GNU Octave in the lessons. It seems that the outputs are indeed obtained from Octave instead of MATLAB. See Issue for more information swcarpentry#37
Hi @franktoffel - this is a great idea. Learners might have trouble setting up MATLAB before/on the day of the workshop, and Octave is a handy replacement. The correct tag, I think, is Also, I'd rather that we not have this line:
Mainly because this may change, and new contributors may use MATLAB-generated figures instead. |
Removed line where it was specified that figures were obtained with Octave because that may change.
You are right @ashwinsrnth. I edited the callout and now should be fine to merge. |
That's great! +1 for merge. |
I'm happy with this, but maybe we can incorporate one more change - rather than saying,
can we instead have something like
My rationale is that there might be other reasons that learners might not be able to work with MATLAB than not having access to a license. |
Hi @ashwinsrnth, thanks for the feedback (again). Why do you imply that Octave will work through most of the lesson? |
I would even argue that it should be a requirement for our MATLAB lessons that they work just as well in Octave. |
On the other hand, in 17 years, I've never met anyone who used Octave
who wasn't already a committed open sourcer and a competent programmer -
I think the overwhelming majority of people we want to reach use
brand-name MATLAB, just as almost every scientist who's doing things
with spreadsheets uses brand-name Excel.
|
While I agree with you, I also think @gvwilson is right (I made an argument similar to yours to him a few months ago :-) Wherever possible, I think we can have callout boxes, etc., pointing to "how to do it with Octave", but I don't think we should promise full compatibility. For instance, we're hoping to have a section on debugging soon, and if I recall correctly, that's done a bit differently on Octave. |
This is more a fundamental question. I completely agree with you (@gvwilson and @ashwinsrnth) regarding how famous "MATLAB" is and I never suggested to change the name of it for that reason. BUT, in my opinion teaching people how to use a commercial product when there is a compatible an excellent alternative (Octave)... makes me wonder why. For instance, @ashwinsrnth why do you want to teach how to use the debugger instead of going to the excellent documentation of the product? Assuming we are talking to beginners, the concepts of debugging (breakpoints, step in/out, etc) seem to work in the same way as MATLAB does with the new Octave version: Doesn't make more sense to create content which is product-free, especially for beginners? |
I think you make fair points, and I was wrong in thinking that MATLAB and Octave have different debugging commands. As you say, the lessons are currently 100% compatible with Octave, and will probably stay that way. I will change my suggested change from:
to
If compatibility issues ever arise, we'll tackle the problem then :-) |
We might soon(ish) try and run a course in octave. I'll let you know if we run into compatibility issues. |
Changes performed according to @ashwinsrnth suggestions ;) |
Added callout box linking to Octave
Thanks, @franktoffel! |
A pleasure, @ashwinsrnth! I also learnt a few new things about Octave doing this PR and arguing about it :) |
Added callout box linking to Octave
This is just a draft but I think it would be nice to reference GNU Octave in the lessons. It seems that the outputs are indeed obtained from Octave instead of MATLAB. See Issue for more information #37
If there is a better format that {.challenge} for this callout, please let me know 👀