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
In the MMKP example (and probably others), if you set !logLpLevel in the MMKP section, it doesn't get applied correctly because when the DecompAlgoC object is created, it only reads parameters in the CUT section and not the MMKP section. I'm not sure exactly what the fix is. Should this be a global parameter instead? Or should the MMKP application set the parameter somehow appropriately? In any case, I guess for now, the file mmkp.parm should be updated to reflect how this parameter should really be set.
The text was updated successfully, but these errors were encountered:
Comment by @tkralphs created at 2011-07-24 17:54:22
Sorry, I forgot that I added logLpLevel to the MMKP section expecting that was the correct place to add it, so there isn't really a problem with mmkp.parm per se. It just might be good if that parameter was set no matter where it appeared. It took me a while to debug that one.
Comment by @tkralphs created at 2011-07-25 00:23:34
LimitTime is in the same boat. I would think it would be a global parameter, but you put it in the DECOMP section. I guess documentation is the real key here.
Issue created by migration from Trac.
Original creator: @tkralphs
Original creation time: 2011-07-24 17:26:35
Assignee: @mgalati13
In the MMKP example (and probably others), if you set !logLpLevel in the MMKP section, it doesn't get applied correctly because when the DecompAlgoC object is created, it only reads parameters in the CUT section and not the MMKP section. I'm not sure exactly what the fix is. Should this be a global parameter instead? Or should the MMKP application set the parameter somehow appropriately? In any case, I guess for now, the file mmkp.parm should be updated to reflect how this parameter should really be set.
The text was updated successfully, but these errors were encountered: