{"id":403849,"date":"2025-01-07T08:36:35","date_gmt":"2025-01-07T08:36:35","guid":{"rendered":"https:\/\/innovationspace.ansys.com\/forum\/forums\/topic\/material-import-broken-in-2024-r23\/"},"modified":"2025-01-07T08:36:35","modified_gmt":"2025-01-07T08:36:35","slug":"material-import-broken-in-2024-r23","status":"publish","type":"topic","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/topic\/material-import-broken-in-2024-r23\/","title":{"rendered":"Material import broken in 2024 R2.3"},"content":{"rendered":"

<p>I recently upgraded my Lumerical installation from 2023 R1.3 to 2024 R2.3. After the upgrade, I noticed that importing materials using sampled (n, k) data no longer works as expected. The issue seems to be in the underlying readdata function, which does not work as expected. Taking the example file on this page<\/a>, and running ?readdata on it produces the following output:<br><br>result: <br>0  3  <br>1  2  <br>2  4  <br>3  3  <\/p><p>This is clearly wrong; it seems that readdata only reads the integer part of each number and ignores everything after the decimal point. <\/p><p>I am running Lumerical on Ubuntu, if that is relevant.<\/p><p>Needless to say, but this is a massive bug, which prevents me from running any (relevant) simulations due to not being able to use imported materials. I would have reported it directly to Ansys, if I had the means to do that. <\/p><\/p>\n","protected":false},"template":"","class_list":["post-403849","topic","type-topic","status-publish","hentry"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t