# Non-breaking space in Model.csv current version (2024Q4)

**URL:** <https://forum.depmap.org/t/non-breaking-space-in-model-csv-current-version-2024q4/4127>\
**Category:** Issues and Bugs\
**Tags:** data\
**Created:** [April 8, 2025, 3:10pm UTC](https://forum.depmap.org/t/non-breaking-space-in-model-csv-current-version-2024q4/4127 "2025-04-08T15:10:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dllahr](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.depmap.org/dllahr/32/23_2.png) [@dllahr](https://forum.depmap.org/u/dllahr)\
**Post date:** [April 8, 2025, 3:10pm UTC](https://forum.depmap.org/t/non-breaking-space-in-model-csv-current-version-2024q4/4127/1 "2025-04-08T15:10:33Z")

</div>

Hi -

Minor but I hit a potential problem using the current (2024Q4) version of Model.csv. For the entry for model ID ACH-000938, for the field ModelSubtypeFeatures, it contains “DUX4” and then some non-breaking spaces encoded/represented in python as \xa0 (repeated 4 times). I don’t think any information is encoded in these so I just deleted them, I am wondering if there should be something else after DUX4 for the ModelSubtypeFeatures for this model.

I discovered the above when trying to save the metadata to an hdf5 format, specifically trying to format as ASCII.

Cheers,  
Dave

---

<div class="post-metadata">

**Author:** ![pmontgom](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.depmap.org/pmontgom/32/4_2.png) [@pmontgom](https://forum.depmap.org/u/pmontgom)\
**Post date:** [April 24, 2025, 2:02pm UTC](https://forum.depmap.org/t/non-breaking-space-in-model-csv-current-version-2024q4/4127/2 "2025-04-24T14:02:19Z")

</div>

Thanks for letting us know.

Yes, it’s probably a data entry mistake that introduced the invisible characters.

We’ll look into adding a validation to our export processes to confirm there aren’t any such characters because I can imagine they are just annoying downstream.

Thanks,  
Phil