bugGNU Octave - Bugs: bug #60129, [octave forge] (image) bwlabel,...

 
 

bug #60129: [octave forge] (image) bwlabel, bwlabeln, and bwconncomp saying "not yet implemented"

Submitter:  None
Submitted:  Fri 26 Feb 2021 09:43:23 PM UTC
   
 
Category:  Octave Package Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Unexpected Error or Warning
Status:  Works For Me Assigned to:  None
Originator Name:  Dany Waller Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 6.2.0
Operating System:  * Mac OS Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sat 28 Aug 2021 02:05:49 PM UTC, comment #7: 

No answer from OP.
closing as "works for me".
If there is still a problem, please open this report again.

Avinoam Kalma <avinoam>
Group Member
Mon 29 Mar 2021 09:46:20 AM UTC, comment #6: 

Change status to "works for me".
Waiting for OP answer.

Avinoam Kalma <avinoam>
Group Member
Sat 27 Mar 2021 07:56:35 PM UTC, comment #5: 

@Dany Waller: Does it now work for you?

The image package contains compiled C functions, and m-file functions. After an Octave update the new Octave version might be able to run the m-file functions of the image package from the previous Octave version, but not the compiled functions (like bwlabel). The commmands from Markus (comment #4) then re-compile the C functions for the new Octave version.

If we do not hear any response from Dany Waller for another 4 weeks, I would suggest to CLOSE this bug report then as WORKS FOR ME.

Hartmut <hardy>
Mon 01 Mar 2021 05:19:40 PM UTC, comment #4: 

Did you recently update to a newer Octave version? If so, you might need to recompile binaries of packages that have been compiled with older Octave versions.
In that case, the following might help:

pkg uninstall image
pkg install -forge image


Markus Mützel <mmuetzel>
Group administrator
Mon 01 Mar 2021 04:14:35 PM UTC, comment #3: 

comment #1:

> What does:
> which bwlabel
> tell you?
>
> On my system (windows) it points to a binary (compiled) file (bwlabeln.oct).
> Maybe on your system the binary image package files aren't present, or they're not in the path, and/or initializing the image package didn't work properly.
>


"which bwlabel" does not produce anything, Octave returns an empty new command line. I don't think it's an initialization problem since I can use other image package commands just fine, so far only these 3 have not worked. I will double check that the binary files exist in the path, thank you!

comment #2:

> In addition to comment #1, did you type
>


> pkg load image


>


Yes, I loaded the image package and it is active in my package list.

Dany Waller <lunarswirls>
Sun 28 Feb 2021 11:51:31 AM UTC, comment #2: 

In addition to comment #1, did you type


pkg load image


Avinoam Kalma <avinoam>
Group Member
Sat 27 Feb 2021 11:48:39 AM UTC, comment #1: 

What does:
which bwlabel
tell you?

On my system (windows) it points to a binary (compiled) file (bwlabeln.oct).
Maybe on your system the binary image package files aren't present, or they're not in the path, and/or initializing the image package didn't work properly.

Philip Nienhuis <philipnienhuis>
Group Member
Fri 26 Feb 2021 09:43:23 PM UTC, original submission:  

I am using Mac OS Catalina, Octave 6.2.0, Image package 2.12.0.
I am trying to run an analysis on a binary image to find the number of connected regions. I initially tried finding connected regions using

map = load('bw_map.png');
L = bwlabel(map,8);

Octave reported that "The 'bwlabel' function belongs to the image package from Octave Forge but has not yet been implemented."
Based on an earlier bug report: I double checked that I loaded the image package, it is active under pkg list, and I tried similar functions bwlabeln and bwconncomp and got the error message for each function, respectively. Other functions from the image package work fine, and I have uninstalled and reinstalled the package with no change. I tried calling each function using help and attached a screenshot with a result, including the active pkg list.
These functions still exist in the image package documentation and do not appear on the depreciated function list, so I am not sure why they are not accessible. Thanks for any suggestions or tips!

Anonymous

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #50929:  Screen@Shot@2021-02-26@at@4.23.12@PM.png added by None (63KiB - image/png - Screenshot of octave output, including function calls and pkg list)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by hardy (Posted a comment)
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by lunarswirls (Posted a comment)
  • -email is unavailable- added by avinoam (Posted a comment)
  • -email is unavailable- added by siko1056 (Updated the item)
  • -email is unavailable- added by None (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 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-08-28 avinoam Open/ClosedOpen Closed
    2021-03-29 avinoam StatusNeed Info Works For Me
    2021-02-27 philipnienhuis StatusNone Need Info
    2021-02-27 siko1056 Summarybwlabel, bwlabeln, and bwconncomp saying &quot;not yet implemented&quot; in Image package [octave forge] (image) bwlabel, bwlabeln, and bwconncomp saying "not yet implemented"
    2021-02-26 None Attached File- Added Screen@Shot@2021-02-26@at@4.23.12@PM.png, #50929

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code