{"id":368913,"date":"2024-05-28T07:42:03","date_gmt":"2024-05-28T07:42:03","guid":{"rendered":"\/forum\/forums\/topic\/mode-strange-mode-result-from-fde-solver\/"},"modified":"2024-05-28T07:57:57","modified_gmt":"2024-05-28T07:57:57","slug":"mode-strange-mode-result-from-fde-solver","status":"closed","type":"topic","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/topic\/mode-strange-mode-result-from-fde-solver\/","title":{"rendered":"MODE: Strange mode result from FDE solver"},"content":{"rendered":"

Hello,<\/span><\/p>\n

I am using Lumerical MODE with an FDE solver to find guided modes in a bent waveguide.<\/span><\/p>\n

After upgrading to Lumerical Version 2024 R1.1, I encounter a strange issue. Sometimes findmodes gives me an output like this:  <\/span>\"\"<\/a><\/p>\n

In this case, findmodes returns the maximum number of modes it is set to find with all modes looking like this.<\/span><\/p>\n

That happens however inconsistently. If I run my script again without changing anything (e.g. setup, solver settings, …), I might find the correct modes or obtain the same strange result again. <\/span>The same error appears also in<\/span> older Lumerical MODE scripts that run reliable on <\/span>previous versions before and on different machines.<\/span><\/p>\n

Does anyone know why this error occurs and how it can be fixed?<\/span><\/p>\n

Thank you for your help. <\/span><\/p>\n","protected":false},"template":"","class_list":["post-368913","topic","type-topic","status-closed","hentry","topic-tag-FDE-1","topic-tag-MODE-1","topic-tag-waveguide-1"],"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\n\t\t\n\t\t\n\t\t