QuantumATK Forum
QuantumATK => General Questions and Answers => Topic started by: Dhirendra on March 7, 2016, 07:58
-
There is a bug in the labfloor update. The labfloor is not being updated is some files are added in a subfolder. I guess this happens when a new folder is created while vnl is opened.
-
That should not be the case. Which files is it that VNL does not load?
-
The behaviour is very unpredictive. Its difficult to say when it starts. But once the labfloor update fails, it never goes normal even if vnl is closed and reopened. It happens when there are subfolders in the project.
-
We need some detailed info track down the issue:
- operating system.
- exact version of VNL-ATK.
- user name on the machine
- directory name of the project you are working in when this happens.
-
I am using CentOS 6.7, ATK 2015.1
There are no spaces in the username or anywhere in the directory. The behaviour is so random, that for me it is not easy to know what will cause the lab floor update fail. But once a project fails to update itself in the labfloor, there is no option but to create another one and copy the files. This is annoying.
-
I understand that this issue is annoying. I need you to open VNL from a Terminal in order to see any error messages that occur when you see the problem. Please report the full contents of any error messages you get. Thanks.
-
I understand that this issue is annoying. I need you to open VNL from a Terminal in order to see any error messages that occur when you see the problem. Please report the full contents of any error messages you get. Thanks.
This will not work on Windows (in case other users have similar problems there) unless you do some tricks first:
1. Make a copy of vnl.exe
2. Make a copy of atkpython.exe
3. Rename the copy of atkpython.exe to vnl.exe
Run this new vnl.exe
-
I guess I have found the cause. I generally use emacs editor to edit the .py files. Sometimes the editor creates hidden files starting with a dot (.) . When I remove these hidden files, the labfloor updates smoothly.
-
Hm, we had that problem a while ago, but I thought it had been was fixed... Should be checked
-
It is fixed in 2016. For 2015 users, just delete those files if you have this problem.