MATLAB: Payment gateway is DOWN

MATLABpayment

Hi there,

I am trying to buy MATLAB but when I want to proceed to the payment the server is DOWN!

Please check it!

Best Answer

Answers is not MATLAB customer support. We have no way to deal with a server being down. Answers is supported by mainly people who are not even MathWorks employees.

So if you have a problem with a server being down, then wait for a few hours. It will probably have been repaired by then. If this is on a weekend and a server is down and you need it immediately, then you may have a problem. But even so, there is nothing we can do here.

If you have waited for a day or so, then send e-mail to the MathWorks. Sometimes things get broken and if nobody tells them, then nobody ever knows to fix something. But again, Answers is not the customer support site.

On the page I give below, you can contact The MathWorks using telephone (during the appropriate hours during the week) or by mail.

http://www.mathworks.com/company/aboutus/contact_us/?s_tid=gn_cntus

Related Solutions

MATLAB: Mex Fortran Gateway Function

OK, here is some code you can try (CAUTION: UNTESTED). Uses the Fortran 95 MATLAB interface code from the FEX I mentioned in an earlier post (compile this first). Just call this file crvfit.f90 and then compile it like this:

mex crvfit.f90 MatlabAPImx.obj

If you run into problems let me know. It is horribly inefficient with regards to memory copying, but I am simply following your strict interface requirements.

#include "fintrf.h"
!---------------------------------------------------------------------
        subroutine mexFunction(nlhs, plhs, nrhs, prhs)
        use MatlabAPImx
        implicit none
  !-ARG
        mwPointer plhs(*), prhs(*)
        integer*4 nlhs, nrhs
  !-LOC
        real(8), pointer :: xfit(:), yfit(:), xfite(:), yfite(:), yfit2(:)
        integer imode, nptsf
        real delfac
  !-----
        ! insert some input argument checks here
        xfit => fpGetPrCopy1(prhs(1))
        yfit => fpGetPrCopy1(prhs(2))
        xfite => fpGetPrCopy1(prhs(3))
        yfite => fpGetPrCopy1(prhs(4))
        imode = mxGetScalar(prhs(5))
        yfit2 => fpGetPrCopy1(prhs(6))
        nptsf = mxGetScalar(prhs(7))
        delfac = mxGetScalar(prhs(8))
        ! check association status of xfit etc here
        call crvfit(xfit,yfit,xfite,yfite,imode,yfit2,nptsf,delfac)
        plhs(1) = mxArray(xfit(1:nptsf))
        plhs(2) = mxArray(yfit(1:nptsf))
        plhs(3) = mxArray(xfite(1:nptsf))
        plhs(4) = mxArray(yfite(1:nptsf))
        plhs(5) = mxArray(dble(imode))
        plhs(6) = mxArray(yfit2(1:nptsf))
        plhs(7) = mxArray(dble(nptsf))
        plhs(8) = mxArray(dble(delfac))
        call fpDeallocate(xfit)
        call fpDeallocate(yfit)
        call fpDeallocate(xfite)
        call fpDeallocate(yfite)
        call fpDeallocate(yfit2)
        end subroutine mexFunction
        subroutine crvfit(xfit,yfit,xfite,yfite,imode,yfit2,nptsf,delfac)
        double precision xfit(*),yfit(*),xfite(*),yfite(*),yfit2(*)
        integer imode
        integer nptsf
        real delfac
        ! etc
        end subroutine

MATLAB: MEX Fortran Gateway and Sparse Matrices

Sparse matrices and full matrices are internally stored differently. For full matrices, all of the matrix values are physically stored in memory (including the 0's). For sparse matrices, only the non-zero values are stored along with row and column index information. You cannot use the same code in a mex routine to access the elements of a full and a sparse matrix. You must have different code for each. The expected result of using full code on a sparse matrix in a mex routine is either (1) wrong results, or (2) MATLAB crash.

The fix is to write specific code in your mex routine to handle sparse matrices. Options would be:

1) Write code to handle the sparse matrix directly
2) Convert the input to full before processing it (NOT recommended since this could be slow and a memory hog)
3) Throw an error if the input is sparse

Without seeing your code and knowing the variable sizes involved it is impossible to advise what approach you should take.

Best Answer

Related Solutions

MATLAB: Mex Fortran Gateway Function

MATLAB: MEX Fortran Gateway and Sparse Matrices

Related Question