pytorch model eval shows progress bar and epochs - eval

after loading a pretrained torch model, I assume that I should run model.eval() and it turns off the gradiants and dropouts, still, Unexpectedly, the progress bar is shown and some epochs start to proceed.
Does anyone have any idea what's the probable reason?

Related

huggingface_load_dataset() function quit() without finishing

I try to use datasets to get "wikipedia/20200501.en" with the code below.The progress bar shows that I just complete 11% of the total dataset, however the script quit without any output in standard outut. I checked the cached directory and find the arrow file is just not completed.
wiki = load_dataset("wikipedia", "20200501.en", split="train", download_config=download_conf)
I tried several times and got different ratio of completion but never succeed in completing the progress.Could any one help me?
env:python version:3.7
datasets version:1.1.2
MacOS
This is caused by unstable network connection. It can be solved by downloading the URL with browser or "wget" function.

Test progress shows 0 percent complete

All of my test runs are showing as in the attached image - in this case all tests have passed, but I am showing 0% progress for the test run.
When I initially start the test run, the progress bar updates - but subsequently disappears.
I don't have any other issues with test data, test cases, plans, etc.
For the record this is tracked here and we're working on this area
https://github.com/kiwitcms/Kiwi/issues/1326

Pepper Error 720

We have a Pepper robot recently and actively trying to develop apps for it. Lately more and more we encounter the same error - 720 (Indication for this error is that the shoulder LED's starts blinking yellow).
When we push the button we hear the following description of the error:
Description: Some of my motors are getting hot in my Neck. I will need to rest soon.
Solution based on the documentation: Robot motors are getting hot or are already too hot to be able to move. Put the robot in crouch and unstiffened and wait for few tens of minutes to let its motors cool down before you can use it again.
Is it normal that we encounter this error several times a day? When we push the button behind the tablet, the error goes away and we can continue our work.
The room temperature is about 22-24 degrees.
Is there something we can do to prevent this error from occurring?
Best Regards.
Also check that you don't have objects near pepper (1m, 1m50 around pepper). If you do, then Pepper might consider those objects as potential kids and consistently try to look down to see them. With time it will heat up the neck because of the head's weight creating torque on the neck.
Constant movement heats up the motor. If you do not need the robot to be alive or moving around when you develop then just put it in resting position.
http://doc.aldebaran.com/2-5/naoqi/motion/control-stiffness-api.html?highlight=relax#ALMotionProxy::rest
If you encounter this error too often, the neck motor might be damaged.
You can contact support using this form: https://www.ald.softbankrobotics.com/en/about-us/contact . They will tell you if your Pepper needs repair.

AngularJS Map Rendring & performance Issue

I implemented google Map with cluster and polyline drawing with vehicle moving on it, and divided map functionality with time slots please check image to get clear understanding,
My Main Problem when large number of lat longs comes in response rendering get hanged for few seconds and also please wait loading (Some time get hanged), Sometimes also result in the no response with the page ,
Please help me with the solutionConsole Errors
Map Image with buttons functionality

How to propery update an image in Nativescript?

I have the requirement to update an image in the App over and over again (displaying some generated data).
But after several intervals the app crashes with out of memory.
I'm updating the image with this line:
(that.detailImage.nativeElement).src = DummyImage.image1;
setting the image as base64-String. I already tried using res:// and external references and even local files. The problem stays: it keeps the memory.
Reducing the size of the image helps only to delay the crash, I even got the crash with an 1kb image, but it took some minutes.
You can find the "running" code at:
https://bitbucket.org/WarEagle/implementationproblems/src/944eedf10a14d60ec421e274760b3c2c3d9ae9a1/ImageTest/?at=master
I'm really interested in understanding what I'm doing wrong. Every solution I found so far said: "make the image smaller" but this only delays the problem.
Greetings
Torsten
p.s. don't wonder about the = undefined in the example-code, this is done because I'm setting the same image over and over again, than it works, but if I update the src-property with another image, it crashes, for this example I used = undefined to reproduce the problem without uploading thousands of images for changing them around.

Resources