You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Eventually, we need to interface those solvers via R's C/C++ interface instead of calling them by plain system calls. Actually, after 5 years I had to cope with a weird issue one more time.
Actually, the reason for the crash was that the NAME field in the file WAS TOO LONG! The following is an excerpts from EAX to import TSPlib instances. Here, the 'word' string is limited to 80 chars and everything above leads to a crash! Who decided to go for this restriction to 80 chars!? Took me >1h of lifetime to figure this one out.
Eventually, we need to interface those solvers via R's C/C++ interface instead of calling them by plain system calls. Actually, after 5 years I had to cope with a weird issue one more time.
Actually, the reason for the crash was that the NAME field in the file WAS TOO LONG! The following is an excerpts from EAX to import TSPlib instances. Here, the 'word' string is limited to 80 chars and everything above leads to a crash! Who decided to go for this restriction to 80 chars!? Took me >1h of lifetime to figure this one out.
The text was updated successfully, but these errors were encountered: