Author Topic: error when view electrostatic_difference_potential of graphene junction.  (Read 12805 times)

0 Members and 1 Guest are viewing this topic.

Offline hung

  • Regular QuantumATK user
  • **
  • Posts: 17
  • Reputation: 0
    • View Profile
hello!
I run a exemple about electrostatic difference potential of graphene junction by VNL. The process is ok, when I view the contour I saw all scale bar is red, it is not true and  affter save image it is white, too bad. please help me repair it!

Offline hung

  • Regular QuantumATK user
  • **
  • Posts: 17
  • Reputation: 0
    • View Profile
this is VNLscrip

Offline Anders Blom

  • QuantumATK Staff
  • Supreme QuantumATK Wizard
  • *****
  • Posts: 5418
  • Country: dk
  • Reputation: 89
    • View Profile
    • QuantumATK at Synopsys
Does the error persist when you change the colormap for instance?

Offline hung

  • Regular QuantumATK user
  • **
  • Posts: 17
  • Reputation: 0
    • View Profile
I don't change the colormap but when change it is persist

Offline Anders Blom

  • QuantumATK Staff
  • Supreme QuantumATK Wizard
  • *****
  • Posts: 5418
  • Country: dk
  • Reputation: 89
    • View Profile
    • QuantumATK at Synopsys
We have seen this problem occur in one other case, so we need to determine under what circumstance it appears. How are you running VNL? The other case was on Windows under VMWare on a Mac.

Offline hung

  • Regular QuantumATK user
  • **
  • Posts: 17
  • Reputation: 0
    • View Profile
my problem is solved. it is not error of VNL, wich is error of PCs hardware. graphiccard is not enough to display. because, when I use a better PC, it ok.

Offline Anders Blom

  • QuantumATK Staff
  • Supreme QuantumATK Wizard
  • *****
  • Posts: 5418
  • Country: dk
  • Reputation: 89
    • View Profile
    • QuantumATK at Synopsys
Just in case someone else has the same problem, we think it's related to the Microsoft OpenGL driver that comes natively with Windows XP and 7. Installing the proper vendor driver for your graphics card seems to solve the issue. We will, nevertheless, make efforts to fix it for ATK 13.8.