Abstract
We report an error in Fig. 13(a) of our article [Opt. Express25, 21286 (2017)], and the correction is presented. Typographical errors in the text are also corrected.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have