Changes between Version 29 and Version 30 of FAQ


Ignore:
Timestamp:
Jan 13, 2011, 6:49:58 PM (10 years ago)
Author:
dtodd
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v29 v30  
    1515'''[#WhydoesSimulationappeartohangorslowdownforlargespinsystems Why does Simulation appear to hang or slow down for large spin systems?]'''
    1616
    17 '''[#MyPyGammaProgramIsUnstableorBehavesBadlyandYetitLooksFine My PyGamma Program Is Unstable or Behaves Badly and Yet it Looks Fine?]'''
     17'''[#MyPyGAMMAProgramIsUnstableorBehavesBadlyandYetitLooksFine My PyGAMMA Program Is Unstable or Behaves Badly and Yet it Looks Fine?]'''
    1818
    1919
     
    3838Note: The time it takes to run these specific jobs is virtually identical in GAMMA versus Simulation - as there is little overhead (e.g. converting arrays between python and C++) when compared to the overall time of the calculations.
    3939
    40 === My PyGamma Program Is Unstable or Behaves Badly and Yet it Looks Fine? ===
    41 Under certain circumstances your pyGamma code can be written in perfectly good Python style yet give unpredictable errors (or no error at all).
     40=== My PyGAMMA Program Is Unstable or Behaves Badly and Yet it Looks Fine? ===
     41Under certain circumstances your PyGAMMA code can be written in perfectly good Python style yet give unpredictable errors (or no error at all).
    4242
    43 We created pyGamma by applying SWIG to GAMMA. In this treatment we did not apply any special code for handling return values that are pointers or references. This has caused non-pythonic behavior to be observed in some situations.
     43We created PyGAMMA by applying SWIG to GAMMA. In this treatment we did not apply any special code for handling return values that are pointers or references. This has caused non-pythonic behavior to be observed in some situations.
    4444
    4545If you have written code that involves subroutines, like this pseudocode,