bugGNU Octave - Bugs: bug #59328, [octave forge] (parallel) package...

 
 

bug #59328: [octave forge] (parallel) package unusable

Submitter:  Muhali <muhali>
Submitted:  Fri 23 Oct 2020 07:54:49 PM UTC
   
 
Category:  Octave Package Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  Invalid / Not an Octave Bug Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * 6.0.90 Operating System:  * GNU/Linux
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Mon 02 Nov 2020 11:51:18 AM UTC, comment #8: 

The relation to bug #58811 was not clear to me, so you might mark this one as a duplicate thereof. Please forgive me for the inappropriate summary, it probably hit me in a frustrated moment.

With your mentioned patch now correctly implemented everything seems to work now. Thank you!

Muhali <muhali>
Sun 01 Nov 2020 04:28:00 PM UTC, comment #7: 

For the separate issue of the missing error I've opened an extra report: bug #59394.

Olaf Till <i7tiol>
Group Member
Sun 01 Nov 2020 11:51:31 AM UTC, comment #6: 

This report should have been posted as a continuation of the closed report #58811. If necessary, closed reports are re-opened.

I'm not sure if I should mark the current report 'duplicate', since the current report was obviously meant to add information.

I thought the described problem was fixed (see #58811), and with the last revision of the parallel package (https://sourceforge.net/p/octave/parallel/ci/039d79e52726414572bd043a728e12b310f6b9cd/) (a some Octave-6 version) I can't reproduce it:


octave:1> pkg load parallel
octave:2> addpath("/tmp")
octave:3> w = parcellfun(1, @foo, {1, 2})
w =

   1   2

octave:4>


Which revision of the development version of the parallel package did you install and how did you install it?

The chosen title of this report is neither informative nor polite. Also, this report seems to mix several issues, which is not helpful. I don't understand the remark about the documentation. If necessary, an extra report with sufficient detail should be opened for this.

Olaf Till <i7tiol>
Group Member
Wed 28 Oct 2020 08:35:29 PM UTC, comment #5: 


comment #2:

> Muhali: What version of the parallel package did you install?


I had version 4.0.0, freshly installed with

pkg install -forge parallel

octave is at version 6.0.91.

Using savepath doesn't change things for me. But it works either way if octave is invoked without -f.

Muhali <muhali>
Wed 28 Oct 2020 07:20:03 PM UTC, comment #4: 

I would like to add, in order for this example to work expected way user must savepath after addpath. The following example works for me. I think that this is a solution for Muhali's problem (without savepath I also get [-1,-1]).


pkg load parallel
addpath tmp
savepath

bar = @(x) foo(x) ;

w = cellfun(@foo, {1, 2})
w = cellfun(bar, {1, 2})
w = parcellfun(1, @foo, {1, 2})
w = parcellfun(1, bar, {1, 2})


Miloš Petrašinović <mpetrasinovic>
Wed 28 Oct 2020 07:07:46 PM UTC, comment #3: 

I just realized I made a beginner's mistake. In 6.0.90a I have used:


pkg install -forge parallel


Actually, the cause of this mistake is that pkg was not removed with the uninstallation of the 6.0.90a version. And I did not realize that I need to uninstall this pkg and install it again.

After pkg reinstall, I do not have a problem anymore.

Miloš Petrašinović <mpetrasinovic>
Wed 28 Oct 2020 06:19:24 PM UTC, comment #2: 

Miloš: Where are you getting the parallel package from?  Is doesn't seem to be included in the copy of Octave 6.0.90 that I installed using the installer that I uploaded to alpha.gnu.org.

Muhali: What version of the parallel package did you install?


John W. Eaton <jwe>
Group administrator
Mon 26 Oct 2020 10:46:21 PM UTC, comment #1: 

For me, this works with 6.0.90a on Win10, but do not work with 6.0.92.

Miloš Petrašinović <mpetrasinovic>
Fri 23 Oct 2020 07:54:49 PM UTC, original submission:  

At least with respect to the documentation the parallel package (parcellfun) is not in a usable state right now. The following setting summarizes what I mean.

Using this function file


## /tmp/foo.m
function y = foo (x)
   y = factorial(x) ;
endfunction


and executing


pkg load parallel
addpath /tmp

bar = @(x) foo(x) ;

w = cellfun(@foo, {1, 2})
w = cellfun(bar, {1, 2})
w = parcellfun(1, @foo, {1, 2})
w = parcellfun(1, bar, {1, 2})


gives the correct (1, 2) and incorrect (-1, -1) results.

This happens with the current and with the dev versions of the package and of octave.

Because no errors are returned, and because the documentation has not been updated since the package has been reworked, at least a strong warning should be issued when it is used.

I find it unfortunate that the old version somehow 'disappeared', which is bound to break many user scripts.

Muhali <muhali>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by i7tiol (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by mpetrasinovic (Posted a comment)
  • -email is unavailable- added by muhali (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-11-02 i7tiol StatusNone Invalid / Not an Octave Bug
        Open/ClosedOpen Closed
    2020-10-23 rik5 Carbon-CopyRemoved 72865 -
    2020-10-23 rik5 CategoryNone Octave Package

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code