QuantumATK Forum

QuantumATK => General Questions and Answers => Topic started by: Tufan on September 29, 2015, 14:28

Title: Error during Device simulation in QuantumWise 2015.rc2
Post by: Tufan on September 29, 2015, 14:28

Getting the following error while running device simulations  in QuantumWise 2015.rc2.


Traceback (most recent call last):
  File "/root/Desktop/MoS2_25_MoS2_9B_DevDOS_Trans_IV.py", line 612, in <module>
    selfconsistent_configurations_filename="ivcurve_selfconsistent_configurations.nc",
  File "./zipdir/NL/Analysis/IVCurve.py", line 151, in __init__
  File "./zipdir/NL/Analysis/IVCurve.py", line 271, in calculateIVCurve
  File "./zipdir/NL/Analysis/IVCurve.py", line 249, in calculateTransmissionAndCurrent
  File "./zipdir/NL/Analysis/TransmissionSpectrum.py", line 117, in __init__
  File "./zipdir/NL/Analysis/BaseTransmissionSpectrum.py", line 131, in __init__
  File "./zipdir/NL/CommonConcepts/QuantityChecks.py", line 273, in setAndCheckInfinitesimal
NL.ComputerScienceUtilities.Exceptions.NLValueError: The parameters, infinitesimal, must a be positive energy.
Traceback (most recent call last):
  File "/root/Desktop/MoS2_25_MoS2_9B_DevDOS_Trans_IV.py", line 612, in <module>
    selfconsistent_configurations_filename="ivcurve_selfconsistent_configurations.nc",
  File "./zipdir/NL/Analysis/IVCurve.py", line 151, in __init__
  File "./zipdir/NL/Analysis/IVCurve.py", line 271, in calculateIVCurve
  File "./zipdir/NL/Analysis/IVCurve.py", line 249, in calculateTransmissionAndCurrent
  File "./zipdir/NL/Analysis/TransmissionSpectrum.py", line 117, in __init__
  File "./zipdir/NL/Analysis/BaseTransmissionSpectrum.py", line 131, in __init__
  File "./zipdir/NL/CommonConcepts/QuantityChecks.py", line 273, in setAndCheckInfinitesimal
NL.ComputerScienceUtilities.Exceptions.NLValueError: The parameters, infinitesimal, must a be positive energy.

Title: Re: Error during Device simulation in QuantumWise 2015.rc2
Post by: Jess Wellendorff on September 29, 2015, 14:30

Yes, we know of this issue. It has been fixed for the 2015 final release. Thanks for reporting it.