661
edits
OctConf 2018 Notes: Difference between revisions
Jump to navigation
Jump to search
→Tuesday: more notes for today
Carandraug (talk | contribs) (→Talking: indent some doc) |
Carandraug (talk | contribs) (→Tuesday: more notes for today) |
||
| Line 42: | Line 42: | ||
; test coverage | ; test coverage | ||
: We can already get the line coverage of our test suite if we run make coverage but that only includes the C++ code. jwe says that it would be simple to add some fields to the interpreter that would allow us to also get the line coverage. This would only be done if Octave was built with specific flags. Oliver pointed out that because of vectorized options, line coverage in m file is not as useful as in other languages since the conditions that in other languages is done with if blocks, are instead done by using indexing with an empty array of an array of false elements. | |||
; measurements of performance | ; measurements of performance | ||
: the test suite is not the best measure of performance. We are estimating that most of its time is spent on running assert which is irrelevant for real Octave programs. It is also mainly cover corner cases and a lot of tests are if it fails when input checking is correct. We should instead have real Octave programs that we used for benchmarking. There wasn't much discussion of this topic beyond noting the problem exists. | |||
; Octave Forge community | ; Octave Forge community | ||
| Line 68: | Line 71: | ||
; packages into Octave core | ; packages into Octave core | ||
: Decided that Octave releases will include some core packages. These will be developed along Octave core, in the same repository, and will be released at the same time. For all purposes they will be a single software project. However, they will still need to be loaded like any other packages. | |||
: Initially, these packages will cover signal processing, statistics, image processing, optimisation, communications, and control. Their aim is to be compatible with their Matlab counterparts and they will be partly imported from the existing Octave Forge packages. | |||
: We won't import all packages in one go. We will start with statistics because we have recently moved a bunch of core functions into it and so they will be easier to import back. signal will probably follow but Pantxo pointed out that this would require a lot of work on its documentation. optim and communications will probably go last since communications is abandoned and optim does not actually have many Matlab compatible functions. | |||
: The current forge packages include extra functions that are not in the Matlab counterparts and their inclusion in the core packages will be decided on a case by case basis. Not sure what will happen with them most likely they would go into a separate package like statistics-legacy. | |||
=== Doing === | === Doing === | ||
; merging of previous GSoC projects | ; merging of previous GSoC projects | ||
: Rik merged Ginesi's special functions and Carlo's worked on merging | : Rik merged Ginesi's special functions and Carlo's worked remotely on merging Cristiano Dorigo's improvement of iterative solvers. | ||
; polygon reconstruction algorithm | ; polygon reconstruction algorithm | ||
: Rik and Pantxo worked on this | : Rik and Pantxo worked on this | ||
; new release | ; new release | ||
: jwe been preparing for wednesday's release | : jwe been preparing for wednesday's release | ||
; dinner in town | ; dinner in town | ||
: That was a very nice time with much discussion about future of Octave and Octave Forge, packages, and makefiles. | |||
; email maintainers mailing list with conclusions | ; email maintainers mailing list with conclusions | ||
: done | |||
== Wednesday == | == Wednesday == | ||