# VectorFunctionSpace solution corresponding to mesh

**URL:** <https://fenicsproject.discourse.group/t/vectorfunctionspace-solution-corresponding-to-mesh/7816>\
**Category:** Uncategorized\
**Created:** [March 9, 2022, 5:15pm UTC](https://fenicsproject.discourse.group/t/vectorfunctionspace-solution-corresponding-to-mesh/7816 "2022-03-09T17:15:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dokken](https://yyz2.discourse-cdn.com/free1/user_avatar/fenicsproject.discourse.group/dokken/32/1560_2.png) [@dokken](https://fenicsproject.discourse.group/u/dokken)\
**Post date:** [March 10, 2022, 2:21pm UTC](https://fenicsproject.discourse.group/t/vectorfunctionspace-solution-corresponding-to-mesh/7816/2 "2022-03-10T14:21:54Z")

</div>

As the velocity space is P2, while your mesh is P1, there is not a 1-to-1 map, such as the P1 space has with `dof_to_vertex_map` and `vertex_to_dof_map` as described [here](https://fenicsproject.discourse.group/t/mapping-from-mesh-coordinates-to-u-vector/5067/2).

For a P2 space, you can use `compute_vertex_values` as shown in: [Save the result of mpirun in a numpy array - #2 by dokken](https://fenicsproject.discourse.group/t/save-the-result-of-mpirun-in-a-numpy-array/6669/2)

---

_[View the full topic](https://fenicsproject.discourse.group/t/vectorfunctionspace-solution-corresponding-to-mesh/7816)._