# CRF with dense features

**URL:** <https://forum.rasa.com/t/crf-with-dense-features/44691>\
**Category:** Rasa Open Source\
**Created:** [June 16, 2021, 9:28am UTC](https://forum.rasa.com/t/crf-with-dense-features/44691 "2021-06-16T09:28:48Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![koaning](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/koaning/32/6626_2.png) [@koaning](https://forum.rasa.com/u/koaning)\
**Post date:** [June 28, 2021, 7:14am UTC](https://forum.rasa.com/t/crf-with-dense-features/44691/21 "2021-06-28T07:14:28Z")

</div>

Ah! I think I may have found it. And I stand corrected. It does seem like the CRF model ignores features. It seems to even ignore the sparse features in the pipeline.

---

<div class="post-metadata">

**Author:** ![koaning](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/koaning/32/6626_2.png) [@koaning](https://forum.rasa.com/u/koaning)\
**Post date:** [June 28, 2021, 7:16am UTC](https://forum.rasa.com/t/crf-with-dense-features/44691/22 "2021-06-28T07:16:09Z")

</div>

Yeah this is definately a bug.

These two pipelines yield the same results.

```auto
pipeline:
  - name: WhitespaceTokenizer
  - name: LanguageModelFeaturizer
    model_name: "roberta"
    model_weights: "roberta-base"
  - name: CRFEntityExtractor

```

```auto
pipeline:
  - name: WhitespaceTokenizer
  - name: CRFEntityExtractor

```

Making a note on the GitHub issue as well.

---

<div class="post-metadata">

**Author:** ![imene\_tar](https://avatars.discourse-cdn.com/v4/letter/i/3ab097/32.png) [@imene\_tar](https://forum.rasa.com/u/imene_tar)\
**Post date:** [June 28, 2021, 7:31am UTC](https://forum.rasa.com/t/crf-with-dense-features/44691/23 "2021-06-28T07:31:11Z")

</div>

Thank you for the time command, I didn’t know it and it will be really helpful for my research.

I have already noticed that the sparse features are not taken into account but I tought that the CRF module generates them automaticaly from the given tokens.

So do you think that the dense features are being ingored (in that case, why would it be different when using DIET without transformer?) or is it simply a bug?

---

<div class="post-metadata">

**Author:** ![imene\_tar](https://avatars.discourse-cdn.com/v4/letter/i/3ab097/32.png) [@imene\_tar](https://forum.rasa.com/u/imene_tar)\
**Post date:** [June 28, 2021, 7:53am UTC](https://forum.rasa.com/t/crf-with-dense-features/44691/24 "2021-06-28T07:53:58Z")

</div>

From what I undestood the time command give the time of the whole testing, is there any command to have the time for the prediction only?

Also, it makes sence that the LM config takes more time in testing because, even if it’s not taken into account, the LM Featurizer in still trained which is computationly expensive.

[Previous page](https://forum.rasa.com/t/crf-with-dense-features/44691.md?page=1)