there is an error when using lp_solve to solve MIP in matlab
in [Matlab]
|
Prev: fread and endian issues
Next: Image brightness
From: dapeng on 16 Jun 2010 10:10 I have MIP,with 64 variables and 30 constrains.I ues lp_solve to solve it.[obj,opt_y]=lp_solve(inte_f',inte_A,inte_b,e,inte_lb,inte_ub,xint); But I get the follow message. get_ptr_sensitivity_rhs: Sensitivity unknown ------------------------------------------------------------------------ Segmentation violation detected at Wed Jun 16 20:03:05 2010 ------------------------------------------------------------------------ Configuration: MATLAB Version: 7.0.0.19920 (R14) Operating System: Microsoft Windows XP Window System: Version 5.1 (Build 2600: Service Pack 3) Processor ID: x86 Family 6 Model 7 Stepping 10, GenuineIntel Virtual Machine: Java 1.4.2 with Sun Microsystems Inc. Java HotSpot(TM) Client VM (mixed mode) Default Charset: ibm-1386_P100-2002 Register State: EAX = 000000f8 EBX = 00000000 ECX = 0000003c EDX = 00000000 ESI = 00000008 EDI = 0d45c6a0 EBP = 00cdc434 ESP = 00cdc42c EIP = 73d0d36e FLG = 00010206 Stack Trace: [0] CRTDLL.DLL:0x73d0d36e(0x0d45c6a0, 8, 240, 864) [1] mxlpsolve.dll:0x019249f7(0x00cdc648, 0x00cdc648, 0, 0) [2] mxlpsolve.dll:0x0192a6aa(0x00cdc648, 0x00cdd300, 0x00cdc794, 0x03f8fc20) [3] mxlpsolve.dll:0x0192a6e7(3, 0x00cdd300, 2, 0x00cdd390) [4] libmex.dll:_mexRunMexFile(3, 0x00cdd300, 2, 0x00cdd390) + 71 bytes [5] libmex.dll:public: virtual void __thiscall Mfh_mex::dispatch_file(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(3, 0x00cdd300, 2, 0x00cdd390) + 157 bytes [6] m_dispatcher.dll:public: virtual void __thiscall Mfh_file::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(3, 0x00cdd300, 2, 0x00cdd390) + 273 bytes [7] m_interpreter.dll:public: void __thiscall ResolverFunctionDesc::CallFunction(int,struct mxArray_tag * * const,int,struct mxArray_tag * * const)(3, 0x00cdd300, 2, 0x00cdd390) + 246 bytes [8] m_interpreter.dll:public: bool __thiscall Resolver::CallMFunction(int,int,class _m_operand * const,union m_operand_storage *,int,class _m_operand * const,union m_operand_storage *,int *)(3, 3, 0x0c15ffe0, 0) + 840 bytes [9] m_interpreter.dll:bool __cdecl inResolveMFunctionCall(struct _m_function_desc *,int,int,class _m_operand * const,union m_operand_storage *,int,class _m_operand * const,union m_operand_storage *,int *,enum inMarshalType *,unsigned int,int,unsigned int *,int)(0x0d2e4590, 3, 3, 0x0c15ffe0) + 148 bytes [10] m_interpreter.dll:bool __cdecl accelMFunctionCall(struct _accelOp *,struct _accelOp * *,struct _accelBytecode *,int *,enum inMarshalType *)(0x0d363010, 0x00cdd9a4 "036\r$谕", 0x02245bc0, 0x00cdd99c) + 108 bytes [11] m_interpreter.dll:int __cdecl accelExec(struct _accelBytecode *,enum inMarshalType *)(0x02245bc0, 0x00cdda1c, 0, 0) + 18462 bytes [12] m_interpreter.dll:_inExecuteHotSegment(0x00cdda50, 0x00cddb20, 0x00cddad0, 0) + 1542 bytes [13] m_interpreter.dll:int __cdecl inInterp(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag volatile *)(1, 845, 85, 0) + 365 bytes [14] m_interpreter.dll:int __cdecl inInterPcodeSJ(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *)(1, 845, 37, 0) + 272 bytes [15] m_interpreter.dll:int __cdecl inExecuteMFunctionOrScript(class Mfh_mp *,bool)(0x0bcab650, 0, 7, 9) + 773 bytes [16] m_interpreter.dll:_inWordsj(2, 0x00cde03c, 7, 0x00cde09c) + 441 bytes [17] m_interpreter.dll:public: void __thiscall Mfh_mp::inRunMP(int,struct mxArray_tag * *,int,struct mxArray_tag * *,struct inWorkSpace_tag *)(2, 0x00cde03c, 7, 0x00cde09c) + 158 bytes [18] m_interpreter.dll:public: virtual void __thiscall Mfh_mp::dispatch_file(struct _mdUnknown_workspace *,int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 2, 0x00cde03c, 7) + 28 bytes [19] m_interpreter.dll:public: virtual void __thiscall Mfh_mp::dispatch_file(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(2, 0x00cde03c, 7, 0x00cde09c) + 26 bytes [20] m_dispatcher.dll:public: virtual void __thiscall Mfh_file::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(2, 0x00cde03c, 7, 0x00cde09c) + 273 bytes [21] m_interpreter.dll:_inDispatchFromStack(657, 0x024e006f "lp_solve", 2, 7) + 891 bytes [22] m_interpreter.dll:_inCallFcnFromReference(0, 0x0bfe5970, 0x789b59c0, 0xcccccccd) + 176 bytes [23] m_interpreter.dll:int __cdecl inInterp(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag volatile *)(1, 0, 94, 0) + 4115 bytes [24] m_interpreter.dll:int __cdecl inInterPcodeSJ(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *)(1, 0, 1, 0) + 272 bytes [25] m_interpreter.dll:int __cdecl inExecuteMFunctionOrScript(class Mfh_mp *,bool)(0x0c056bb0, 1, 0, 0x0c056bb0) + 773 bytes [26] m_interpreter.dll:_inExecCompScript(0, 0x00cde71c, 0x0c056bb0, 0xffffffff) + 321 bytes [27] m_interpreter.dll:public: void __thiscall Mfh_mp::inRunMP(int,struct mxArray_tag * *,int,struct mxArray_tag * *,struct inWorkSpace_tag *)(0, 0x00cde71c, 0, 0x00cde77c) + 122 bytes [28] m_interpreter.dll:public: virtual void __thiscall Mfh_mp::dispatch_file(struct _mdUnknown_workspace *,int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 0, 0x00cde71c, 0) + 28 bytes [29] m_interpreter.dll:public: virtual void __thiscall Mfh_mp::dispatch_file(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 0x00cde71c, 0, 0x00cde77c) + 26 bytes [30] m_dispatcher.dll:public: virtual void __thiscall Mfh_file::dispatch_fh(int,struct mxArray_tag * *,int,struct mxArray_tag * *)(0, 0x00cde71c, 0, 0x00cde77c) + 273 bytes [31] m_interpreter.dll:_inDispatchFromStack(581, 0x02313424 "test1", 0, 0) + 891 bytes [32] m_interpreter.dll:enum opcodes __cdecl inDispatchCall(char const *,int,int,int,int *,int *)(0x02313424 "test1", 581, 0, 0) + 111 bytes [33] m_interpreter.dll:int __cdecl inInterp(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag volatile *)(2, 0, 0, 0) + 2411 bytes [34] m_interpreter.dll:int __cdecl inInterPcodeSJ(enum inDebugCheck,int,int,enum opcodes,struct inPcodeNest_tag *)(2, 0, 0, 0) + 272 bytes [35] m_interpreter.dll:_inInterPcode(2, 0x7876f2d8, 0, 0) + 69 bytes [36] m_interpreter.dll:enum inExecutionStatus __cdecl in_local_call_eval_function(int *,struct _pcodeheader *,int *,struct mxArray_tag * * const,enum inDebugCheck)(0x00cdf2c8, 0x00cdf3bc, 2, 0x0bc80160 "test1\n") + 162 bytes [37] m_interpreter.dll:$L72592(0x7876f2d8, 0x0bc80160 "test1\n", 6, 0) + 196 bytes [38] m_interpreter.dll:enum inExecutionStatus __cdecl inEvalCmdWithLocalReturnandtype(char const *,int *,enum inDebugCheck)(0, 2, 1, 0x00cdf44c "趑�) + 86 bytes [39] m_interpreter.dll:_inEvalCmdNoEnd(0x0bc80160 "test1\n", 0x00cdf4e4, 0x00cdf4a0, 0x024e1ef8) + 16 bytes [40] bridge.dll:_mnParser(0x7c80b741, 0x024e1ef8, 0, 0) + 431 bytes [41] mcr.dll:public: void __thiscall mcrInstance::mnParser(void)(271241, 0x6d5c3a44, 0x616c7461, 0x69625c62) + 87 bytes [42] MATLAB.exe:0x00401d2f(4194304, 0, 271241, 0x024e1ef8) [43] MATLAB.exe:0x00403e45(3276853, 3276849, 0x7ffda000, 0x8054c6ed) [44] kernel32.dll:0x7c817077(0x00403cc0 "jth(U@", 0, 0, 0) This error was detected while a MEX-file was running. If the MEX-file is not an official MathWorks function, please examine its source code for errors. Please consult the External Interfaces Guide for information on debugging MEX-files. If it is an official MathWorks function, please follow these steps in reporting this problem to The MathWorks so that we have the best chance of correcting it: 1. Send this crash report to segv@... for automated analysis. For your convenience, this information has been recorded in: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\matlab_crash_dump.1084 2. Also, if the problem is reproducible, send the crash report to support@... along with: - A specific list of steps that will reproduce the problem - Any M, MEX, MDL or other files required to reproduce the problem - Any error messages displayed to the command window A technical support engineer will contact you with further information. Thank you for your assistance. Please save your workspace and restart MATLAB before continuing your work. Error in ==> lp_solve at 88 [obj, x, duals] = mxlpsolve('get_solution', lp); Error in ==> test1 at 94 [obj,opt_y]=lp_solve(inte_f',inte_A,inte_b,e,inte_lb,inte_ub,xint); What's wrong with it?
From: Steven Lord on 16 Jun 2010 10:39 "dapeng " <gaodapeng1987(a)126.com> wrote in message news:hvam00$l0e$1(a)fred.mathworks.com... >I have MIP,with 64 variables and 30 constrains.I ues lp_solve to solve > it.[obj,opt_y]=lp_solve(inte_f',inte_A,inte_b,e,inte_lb,inte_ub,xint); > But I get the follow message. > get_ptr_sensitivity_rhs: Sensitivity unknown *snip* > Error in ==> lp_solve at 88 > [obj, x, duals] = mxlpsolve('get_solution', lp); > > Error in ==> test1 at 94 > [obj,opt_y]=lp_solve(inte_f',inte_A,inte_b,e,inte_lb,inte_ub,xint); > > > What's wrong with it? You're probably going to have to ask the person that provided you with the lp_solve function (and the helper MEX-file mxlpsolve that it calls.) The crash log file indicates that the failure occurred inside that MEX-file. -- Steve Lord slord(a)mathworks.com comp.soft-sys.matlab (CSSM) FAQ: http://matlabwiki.mathworks.com/MATLAB_FAQ To contact Technical Support use the Contact Us link on http://www.mathworks.com
From: us on 16 Jun 2010 10:49 "dapeng " <gaodapeng1987(a)126.com> wrote in message <hvam00$l0e$1(a)fred.mathworks.com>... > I have MIP,with 64 variables and 30 constrains.I ues lp_solve to solve > it.[obj,opt_y]=lp_solve(inte_f',inte_A,inte_b,e,inte_lb,inte_ub,xint); > But I get the follow message. > get_ptr_sensitivity_rhs: Sensitivity unknown > > ------------------------------------------------------------------------ > Segmentation violation detected at Wed Jun 16 20:03:05 2010 > ------------------------------------------------------------------------ > > Configuration: > MATLAB Version: 7.0.0.19920 (R14) > Operating System: Microsoft Windows XP > Window System: Version 5.1 (Build 2600: Service Pack 3) > Processor ID: x86 Family 6 Model 7 Stepping 10, GenuineIntel > Virtual Machine: Java 1.4.2 with Sun Microsystems Inc. Java HotSpot(TM) > Client VM > (mixed mode) > Default Charset: ibm-1386_P100-2002 > > Register State: > EAX = 000000f8 EBX = 00000000 > ECX = 0000003c EDX = 00000000 > ESI = 00000008 EDI = 0d45c6a0 > EBP = 00cdc434 ESP = 00cdc42c > EIP = 73d0d36e FLG = 00010206 > > Stack Trace: > [0] CRTDLL.DLL:0x73d0d36e(0x0d45c6a0, 8, 240, 864) % <- ! make sure the MEX-file was compiled for your OS... us
From: dapeng on 19 Jun 2010 05:39 "Steven Lord" <slord(a)mathworks.com> wrote in message <hvanng$m56$1(a)fred.mathworks.com>... > > "dapeng " <gaodapeng1987(a)126.com> wrote in message > news:hvam00$l0e$1(a)fred.mathworks.com... > >I have MIP,with 64 variables and 30 constrains.I ues lp_solve to solve > > it.[obj,opt_y]=lp_solve(inte_f',inte_A,inte_b,e,inte_lb,inte_ub,xint); > > But I get the follow message. > > get_ptr_sensitivity_rhs: Sensitivity unknown > > *snip* > > > Error in ==> lp_solve at 88 > > [obj, x, duals] = mxlpsolve('get_solution', lp); > > > > Error in ==> test1 at 94 > > [obj,opt_y]=lp_solve(inte_f',inte_A,inte_b,e,inte_lb,inte_ub,xint); > > > > > > What's wrong with it? > > You're probably going to have to ask the person that provided you with the > lp_solve function (and the helper MEX-file mxlpsolve that it calls.) The > crash log file indicates that the failure occurred inside that MEX-file. > > -- > Steve Lord > slord(a)mathworks.com > comp.soft-sys.matlab (CSSM) FAQ: http://matlabwiki.mathworks.com/MATLAB_FAQ > To contact Technical Support use the Contact Us link on > http://www.mathworks.com > Thanks Steve Lord and us! After that I used lp_solve to MIP,which size is 11*28, then I got the empty value. When 4*3 MIP is solved, I can get the optimal solution quickly. So what's wrong with it? Does the MIP exceed the maximum size for lp_solve. Please help me.Thanks in advance.
From: Steven Lord on 22 Jun 2010 15:37
"dapeng " <gaodapeng1987(a)126.com> wrote in message news:hvi37o$dev$1(a)fred.mathworks.com... > "Steven Lord" <slord(a)mathworks.com> wrote in message > <hvanng$m56$1(a)fred.mathworks.com>... >> >> "dapeng " <gaodapeng1987(a)126.com> wrote in message >> news:hvam00$l0e$1(a)fred.mathworks.com... >> >I have MIP,with 64 variables and 30 constrains.I ues lp_solve to solve >> > it.[obj,opt_y]=lp_solve(inte_f',inte_A,inte_b,e,inte_lb,inte_ub,xint); >> > But I get the follow message. >> > get_ptr_sensitivity_rhs: Sensitivity unknown >> >> *snip* >> >> > Error in ==> lp_solve at 88 >> > [obj, x, duals] = mxlpsolve('get_solution', lp); >> > >> > Error in ==> test1 at 94 >> > [obj,opt_y]=lp_solve(inte_f',inte_A,inte_b,e,inte_lb,inte_ub,xint); >> > >> > >> > What's wrong with it? >> >> You're probably going to have to ask the person that provided you with >> the lp_solve function (and the helper MEX-file mxlpsolve that it calls.) >> The crash log file indicates that the failure occurred inside that >> MEX-file. >> >> -- >> Steve Lord >> slord(a)mathworks.com >> comp.soft-sys.matlab (CSSM) FAQ: >> http://matlabwiki.mathworks.com/MATLAB_FAQ >> To contact Technical Support use the Contact Us link on >> http://www.mathworks.com Thanks Steve Lord and us! After that I used >> lp_solve to MIP,which size is 11*28, then I got the empty value. When 4*3 >> MIP is solved, I can get the optimal solution quickly. > So what's wrong with it? Does the MIP exceed the maximum size for > lp_solve. > Please help me.Thanks in advance. I have no idea. It's not a function that's part of MATLAB or any of the toolboxes provided by The MathWorks, and I don't have any experience using it. As I said above, I think you're going to need to ask whomever wrote lp_solve and/or its helper MEX-file for help debugging this. If you can't reach that person, ask the person from whom you obtained lp_solve. -- Steve Lord slord(a)mathworks.com comp.soft-sys.matlab (CSSM) FAQ: http://matlabwiki.mathworks.com/MATLAB_FAQ To contact Technical Support use the Contact Us link on http://www.mathworks.com |