# Plugin error- feature table summarize

**URL:** https://forum.qiime2.org/t/plugin-error-feature-table-summarize/1717
**Category:** User Support
**Tags:** summarize, metadata, feature-table
**Created:** [November 3, 2017, 4:05pm UTC](https://forum.qiime2.org/t/plugin-error-feature-table-summarize/1717 "2017-11-03T16:05:06Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![mingala](https://forum.qiime2.org/user_avatar/forum.qiime2.org/mingala/32/638_2.png) [@mingala](https://forum.qiime2.org/u/mingala)
#### Post date: [November 3, 2017, 4:05pm UTC](https://forum.qiime2.org/t/plugin-error-feature-table-summarize/1717/1 "2017-11-03T16:05:06Z")

</div>

Hello all,

I am trying to run this part of the QIIME2 pipleine:

```bash
> qiime feature-table summarize \
> --i-table table.qza \
> --o-visualization table.qzv \
> --m-sample-metadata-file /home/mingala/array1/metadata.tsv

```

When i run this code, I get the following error:

```bash
Plugin error from feature-table:

  "None of [Index(['ARLI-C-251689', 'ARLI-G-251716', 'RHAE-C-251185', 'DERO-C-251190',\n 'CHAU-G-251504', 'STLI-G-251197', 'DERO-G-251330', 'PTME-G-251393',\n 'TRCI-G-251383', 'MYKE-G-251195', 'MYKE-G-251331', 'MORU-G-251452',\n 'CHAU-G-251508', 'DERO-G-251344', 'SABI-G-251458', 'ARLI-G-251687',\n 'PTDA-C-251720', 'ARLI-G-251709', 'CASO-C-251367', 'RHAE-G-251163',\n 'STLI-C-251414', 'TRCI-C-251419', 'TRCI-C-251428', 'MYKE-G-251194',\n 'STLI-C-251203', 'LOEV-G-251729', 'MORU-G-251168', 'MYKE-C-251211',\n 'PTME-G-251368', 'URBI-C-251430', 'SABI-C-251699', 'MORU-G-251439',\n 'ARLI-C-251711', 'SABI-G-251697', 'TRCI-C-251516', 'MORU-C-251181',\n 'RHNA-C-251781', 'PTDA-C-251708', 'GLSO-C-251770', 'DEPH-C-251530',\n 'CHAU-G-251509', 'ARLI-C-251715', 'SABI-C-251702', 'MORU-C-251177',\n 'DEWA-C-251535', 'PTME-C-251316', 'EUNA-C-251381', 'DEPH-C-251421',\n 'MORU-C-251441', 'RHAE-G-251553', 'CASO-C-251362', 'MYKE-C-251338',\n 'EXT-NEG', 'DERO-G-251340', 'PCR-NEG'],\n dtype='object')] are in the [index]"

Debug info has been saved to /tmp/qiime2-q2cli-err-uznqgxp5.log

```

I checked that the sample IDs match by running the code without passing --m-sample-metadata, and the resulting table.qsv has the correct sample IDs identical to those in my metadata file. The file was validated with Keemei with no errors.

I even tried to run it again, this time replacing the metadata #SampleID column with the full file names from the MiSeq like so:

![image](https://forum-qiime2-org.s3.dualstack.us-west-2.amazonaws.com/original/1X/0082c0f6aaa7fbee7fd793b93f715991aa608187.png)ARLI-C-251689\_S41\_L001\_R1\_001.fastq.gz

But this threw the same error code. Any ideas about why? Thank you!

---

<div class="post-metadata">

### Author: ![ebolyen](https://forum.qiime2.org/user_avatar/forum.qiime2.org/ebolyen/32/11_2.png) [@ebolyen](https://forum.qiime2.org/u/ebolyen)
#### Post date: [November 3, 2017, 10:44pm UTC](https://forum.qiime2.org/t/plugin-error-feature-table-summarize/1717/3 "2017-11-03T22:44:46Z")

</div>

Hey @mingala,

> [@mingala](#):
>
> I checked that the sample IDs match by running the code without passing --m-sample-metadata, and the resulting table.qsv has the correct sample IDs identical to those in my metadata file.

That's pretty strange. Would you be able to DM me (or post if it's not sensitive) your metadata file and your feature-table? There must be something subtle happening that's causing this.

Thanks!

---

<div class="post-metadata">

### Author: ![mingala](https://forum.qiime2.org/user_avatar/forum.qiime2.org/mingala/32/638_2.png) [@mingala](https://forum.qiime2.org/u/mingala)
#### Post date: [November 4, 2017, 3:47pm UTC](https://forum.qiime2.org/t/plugin-error-feature-table-summarize/1717/5 "2017-11-04T15:47:49Z")

</div>

Thanks for the reply, @ebolyen

Here is the head of the table that results from running the command without -m sample metadata:

 ![52 AM](https://forum-qiime2-org.s3.dualstack.us-west-2.amazonaws.com/original/1X/98b07f50a96e6aa99cd89c3d12df0244df321516.png)

And here is my metadata file:

[ColonGuanometadata.tsv](https://cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com/flex002/uploads/qiime21/original/1X/b4f2015c0548f6caa4ae52b9328acddb9859d1da.tsv) (7.5 KB)

So far all the names seem to match, which is why I cannot figure out why it produces the error.

---

<div class="post-metadata">

### Author: ![thermokarst](https://forum.qiime2.org/letter_avatar_proxy/v4/letter/t/8e7dd6/32.png) [@thermokarst](https://forum.qiime2.org/u/thermokarst)
#### Post date: [November 4, 2017, 3:53pm UTC](https://forum.qiime2.org/t/plugin-error-feature-table-summarize/1717/6 "2017-11-04T15:53:49Z")

</div>

Hi @mingala! If you look carefully, you will notice that your IDs actually aren't quite the same between files:

`ARLI_C_251689` (in your metadata file) vs `ARLI-C-251689` (in your feature table) --- note the underscores vs dashes.

If you update your sample metadata file to use dashes you should be in good shape (technically you could also update your feature table to use underscores, but that would be a lot more work --- it would require reimporting your data with new ID values and reprocessing to this point, which is why I am recommending just updating your metadata file)! Keep us posted! 🦖

---

<div class="post-metadata">

### Author: ![mingala](https://forum.qiime2.org/user_avatar/forum.qiime2.org/mingala/32/638_2.png) [@mingala](https://forum.qiime2.org/u/mingala)
#### Post date: [November 6, 2017, 4:53pm UTC](https://forum.qiime2.org/t/plugin-error-feature-table-summarize/1717/7 "2017-11-06T16:53:09Z")

</div>

Wow...that was very silly. But that is what I get from staring at this stuff for too long I guess....thanks a lot!

---

<div class="post-metadata">

### Author: ![system](https://forum-qiime2-org.s3.dualstack.us-west-2.amazonaws.com/original/3X/2/1/21af5fe23cb6f4579467c66a9ed94e55274ca7bd.svg) [@system](https://forum.qiime2.org/u/system)
#### Post date: [December 7, 2017, 10:53pm UTC](https://forum.qiime2.org/t/plugin-error-feature-table-summarize/1717/8 "2017-12-07T22:53:13Z")

</div>

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
