Correction to: Scientific Reports https://doi.org/10.1038/s41598-019-46676-w, published online 17 July 2019
This Article contains errors. In Figure 1a, the incorrect image was used for panel a3, and the labelling of these panels was inconsistent. The correct Figure and Legend appears below, in Fig. 1.
The scale bars provided in Figure 2c are incorrect. The correct Figure 2c appears below as Fig. 2, with information on magnification provided in the legend.
The Supplementary Information did not include full-length gel images. Uncropped images for gels used in Figure 2b and 3b are provided below as Fig. 3.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Open Access This article is licensed under a Creative Commons Attribution 4.0 International License, which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. The images or other third party material in this article are included in the article’s Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the article’s Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/.
About this article
Cite this article
Vianello, E., Dozio, E., Bandera, F. et al. Author Correction: Dysfunctional EAT thickness may promote maladaptive heart remodeling in CVD patients through the ST2-IL33 system, directly related to EPAC protein expression. Sci Rep 10, 1182 (2020). https://doi.org/10.1038/s41598-020-58143-y
Published:
DOI: https://doi.org/10.1038/s41598-020-58143-y
- Springer Nature Limited
We’re sorry, something doesn't seem to be working properly.
Please try refreshing the page. If that doesn't work, please contact support so we can address the problem.