fsaxen / parforprogmon Goto Github PK

Problem Description

It seems matlab cannot access ppm.increment() within parfor.

Error using testParforProgressbar (line 21)
Dot indexing is not supported for variables of this type.

Steps to Reproduce the Problem

Run the testParforProgressbar.m example.

Specifications

• MATLAB Release: R2020b
• Operating System:
• ParforProgressbar version (or commit link/hash):

Additional Information

Probably matlab has changed how it brodcasts variables in the last updates. Does anyone know how to get it back to work?

More info: The root cause seems to be that the object is not created within the parfor loop. I've tried using step = @() ppm.increment to get rid of the dot indexing problem, however using that approach, there is no increment in the progressbar.

Nice repo! Very useful for my long running parpool job. One minor suggestion would be to specify the minimum version of Matlab for this to work, which I believe is Matlab 2018a. Otherwise, you'll encounter this error https://www.mathworks.com/matlabcentral/answers/395534-how-to-preallocate-tables-using-the-table-function

Problem Description

Before the first iteration is completed, the estimated time is "Inf week", this should be changed to something more meaningful like "Waiting", "Waiting for the first iteration to complete", "Estimating ETA..." or something similar.

Hey! I've been experimenting with thread-based pools recently and I haven't been able to get the progressbar working with it so far, is it not compatible or am I missing something? Thanks

Is your feature request related to a problem? Please describe.
As of now, the tool requires the Instrument Control Toolbox to use udp. While many users have access to this toolbox as part of their license (e.g. Academic), many others don't (this is a complaint seen on FEX).

Describe the solution you'd like
There are alternatives to the udp function that is provided by the paid toolbox. To name a couple: TCP/UDP/IP Toolbox and A simple UDP communications application. There is also an open-source implementation of udp in Octave, which could be adapted for this.

With some effort it might be possible to remove this dependency, and instead rely on some OS-specific APIs.

Additional context
N/A.

Problem Description

I'm having an issue where the titles of the bars disappear after a short while. It looks like this:

(Although it's mildly amusing that some workers reach >100%, it's not the main issue here :) ).

Steps to Reproduce the Problem

This is how I use the tool:

ppm = ParforProgressbar(nGuesses, 'title', 'someTitle',...
        'showWorkerProgress', true, 'progressBarUpdatePeriod', 10);
tic
parfor ind1 = 1:nGuesses
  someFunction(someInput);
  ppm.increment(); %#ok<PFBNS>
end
toc 
delete(ppm); clear ppm;

Initially, the progressbar window appears with all the labels, then it "reopens" several times after which the labels become blank. Here's a screen capture:

Specifications

• MATLAB Release: R2019a
• Operating System: Win10.
• ParforProgressbar version (or commit link/hash): 7e84b2d

Additional Information

In the off-chance that this is some graphical glitch, I'll mention that I'm connected to the machine that runs MATLAB using RDP (remote desktop), where the terminal runs Win7.

Starting in Matlab 2022a, I am getting the following warning:

Warning: udp will be removed in a future release. Use udpport instead.

I found this Mathworks page with information about the transition:
https://www.mathworks.com/help/releases/R2022a/instrument/transition-your-code-to-udpport-interface.html

Problem Description

When I use this function in my custom function and set the iteration number like 1 or 7..., the monitor will cost more time than the loop-self cost.

Steps to Reproduce the Problem

set the iteration number a small number

Specifications

• MATLAB Release: R2019b
• Operating System: Windows CPU i9-9900KF, the number of cores: 8
• ParforProgressbar version (4):