org.nlogo.nvm.ArgumentTypeException: ITEM expected input to be a string or list but got the number 0 instead.

GitHub | ToonTalk | 3 months ago
  1. 0

    Error in ITEM but user code visible

    GitHub | 3 months ago | ToonTalk
    org.nlogo.nvm.ArgumentTypeException: ITEM expected input to be a string or list but got the number 0 instead.
  2. 0

    Exceptions raised while running experiments headless can cause huge log files

    GitHub | 3 months ago | ToonTalk
    org.nlogo.nvm.ArgumentTypeException: ASK expected input to be an agent or agentset but got the number 0 instead.
  3. 0

    Netlogo-how to make a turtle turn at a specification?

    Stack Overflow | 1 year ago | J.Chen
    org.nlogo.nvm.ArgumentTypeException: REMOVE expected input to be a string or list but got the number 0 instead.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Running a model several times with BehaviorSpace

    Stack Overflow | 2 years ago | Nell
    org.nlogo.nvm.ArgumentTypeException: OF expected input to be a turtle agentset or patch agentset or turtle or patch but got NOBODY instead. at org.nlogo.prim._asm_proceduremovewithinpolygon_ifelse_86.perform(:4)

    Root Cause Analysis

    1. org.nlogo.nvm.ArgumentTypeException

      ITEM expected input to be a string or list but got the number 0 instead.

      at org.nlogo.nvm.CommandTask.perform()
    2. org.nlogo.nvm
      CommandTask.perform
      1. org.nlogo.nvm.CommandTask.perform(Task.scala:87)
      1 frame
    3. org.nlogo.prim
      _foreach.perform
      1. org.nlogo.prim.etc._foreach.perform(_foreach.scala:36)
      1 frame
    4. org.nlogo.nvm
      Context.callReporterProcedure
      1. org.nlogo.nvm.Context.callReporterProcedure(Context.java:243)
      1 frame