java.lang.IndexOutOfBoundsException

Number of sites and genotypes do not agree

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web237

  • via Google Groups by Marlee Labroo, 6 months ago
    Number of sites and genotypes do not agree
  • position (0) must be less than the number of elements that remained (0)
  • via blogspot.com by Unknown author, 11 months ago
    String array index number (3) must not be greater than size (2)
  • Stack trace

    • java.lang.IndexOutOfBoundsException: Number of sites and genotypes do not agree at net.maizegenetics.dna.snp.GenotypeTableBuilder.addTaxon(GenotypeTableBuilder.java:569) at net.maizegenetics.analysis.gbs.v2.ProductionSNPCallerPluginV2.callGenotypes(ProductionSNPCallerPluginV2.java:294) at net.maizegenetics.analysis.gbs.v2.ProductionSNPCallerPluginV2.lambda$processData$105(ProductionSNPCallerPluginV2.java:264) at java.util.Iterator.forEachRemaining(Unknown Source) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Unknown Source) at java.util.stream.ReferencePipeline$Head.forEach(Unknown Source) at net.maizegenetics.analysis.gbs.v2.ProductionSNPCallerPluginV2.processData(ProductionSNPCallerPluginV2.java:263) at net.maizegenetics.plugindef.AbstractPlugin.performFunction(AbstractPlugin.java:110) at net.maizegenetics.plugindef.AbstractPlugin.dataSetReturned(AbstractPlugin.java:1645) at net.maizegenetics.plugindef.ThreadedPluginListener.run(ThreadedPluginListener.java:29) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)[pool-1-thread-1]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.