Author Topic: Virtual NanoLab Error  (Read 3765 times)

0 Members and 1 Guest are viewing this topic.

Offline Akan

  • New QuantumATK user
  • *
  • Posts: 2
  • Country: za
  • Reputation: 0
    • View Profile
Virtual NanoLab Error
« on: April 12, 2017, 12:51 »
Dear All,
During my free trial of VNL-ATK , all attempts to use the BUILDER to load a simple structure has failed. In all cases, the error is:

Traceback (most recent call last):
  File "C:\Program Files (x86)\QuantumWise\VNL-ATK-2016.4\Lib\site-packages\AddOns\GrapheneBuilders\GrapheneBuilders.py", line 416, in _build
    structure = self._generateStructure()
  File "C:\Program Files (x86)\QuantumWise\VNL-ATK-2016.4\Lib\site-packages\AddOns\GrapheneBuilders\GrapheneBuilders.py", line 466, in _generateStructure
    bond_length = widget._distance.value()*Angstrom
  File ".\zipdir\NL\CommonConcepts\PhysicalQuantity.py", line 2004, in __mul__
NLValueError: Multiplying the unit Ang with "None" of type <type 'NoneType'> failed.
[/size]

What causes this error, and how can it be resolved? Thanks a lot for suggestions.

Regards,
Akan

Offline Petr Khomyakov

  • QuantumATK Staff
  • Supreme QuantumATK Wizard
  • *****
  • Posts: 1290
  • Country: dk
  • Reputation: 25
    • View Profile
Re: Virtual NanoLab Error
« Reply #1 on: April 12, 2017, 14:01 »
Please could you describe step-by-step what you did to get this error? 

Offline Akan

  • New QuantumATK user
  • *
  • Posts: 2
  • Country: za
  • Reputation: 0
    • View Profile
Re: Virtual NanoLab Error
« Reply #2 on: April 12, 2017, 14:23 »
After Installation:
(1).   Right-click on the Virtual NanoLab 2016.4 icon.
(2).   Click ‘Open’ to initiate an instance of Virtual NanoLab… an icon pops up saying ‘Loading Projects’. It actually takes a considerably long time to load all projects…In fact, more than 10 minutes!
(3).   Click ‘Projects’ tab, and create a new project “Trial’.
(4).   Click BUILDER.
(5).   On the Builder menu, click ‘File’, ‘add’, 'From Plugin', 'Nanosheet'.
(6).   Set n =4 and m= 4.
(7).   Click ‘Build’.

 The same Virtual NanoLab  error message pops up.
« Last Edit: April 12, 2017, 15:03 by Akan »

Offline Petr Khomyakov

  • QuantumATK Staff
  • Supreme QuantumATK Wizard
  • *****
  • Posts: 1290
  • Country: dk
  • Reputation: 25
    • View Profile
Re: Virtual NanoLab Error
« Reply #3 on: April 12, 2017, 15:36 »
Regarding #2 How many projects do you have? This step takes no time for me.

Regarding the error message, I cannot reproduce it in ATK-2016.4 in Windows 10. Could you check if you have the latest GrapheneBuilder plugin installed? For that, you should select Help in the VNL menu, then click on AddOn Manager, and finally do search for GrapheneBuilders plugin and update it, if needed.   

Offline Freas

  • New QuantumATK user
  • *
  • Posts: 1
  • Country: us
  • Reputation: 0
    • View Profile
Re: Virtual NanoLab Error
« Reply #4 on: August 10, 2017, 09:08 »
Regarding #2 How many projects do you have? This step takes no time for me.

Regarding the error message, I cannot reproduce it in ATK-2016.4 in Windows 10. Could you check if you have the latest Male Extra GrapheneBuilder plugin installed? For that, you should select Help in the VNL menu, then click on AddOn Manager, and finally do search for GrapheneBuilders plugin and update it, if needed.

I think it's a windows problem. I had the issue on windows 7 but after upgrading to windows 10 it went away so..
« Last Edit: March 25, 2018, 16:11 by Freas »

Offline Petr Khomyakov

  • QuantumATK Staff
  • Supreme QuantumATK Wizard
  • *****
  • Posts: 1290
  • Country: dk
  • Reputation: 25
    • View Profile
Re: Virtual NanoLab Error
« Reply #5 on: August 10, 2017, 09:16 »
Thanks for letting us know.

Offline Anders Blom

  • QuantumATK Staff
  • Supreme QuantumATK Wizard
  • *****
  • Posts: 5410
  • Country: dk
  • Reputation: 89
    • View Profile
    • QuantumATK at Synopsys
Re: Virtual NanoLab Error
« Reply #6 on: August 15, 2017, 05:38 »
This bug is fixed in 2017; it has to do with comma vs. point representation of the decimal sign in certain locales, but it's quite complex so it's hard to update 2016.4, and since all academic users can access VNL 2017 for free we decided not to make a 2016.5. Thus, the "fix" is to upgrade to 2017.