Author's response—Letter to the Editor (FSI-D-16-00737). (January 2017)