10 Reputation

2 Badges

3 years, 91 days

MaplePrimes Activity

These are replies submitted by abecke12

@tomleslie The ifelse page by Maplesoft only shows those two possible cases, it pretty much implies you can only do `if`(c,a,b), in a restricted fashion. The example from Carl Love showed me that you can get around those implied limitations with squiggly thinking!

@acer I'm going to try turning this procedure into a 1D input form as practice. (I 'converted' it and it did execute in under a second, but I want to be sure I understand how it loads packages and such.) I shall enact your suggestions for future worksheets! Maybe it will even stop the memory sink, and it shall definitely stop the irritating lags that I already knew were a by-product of working in 2D input...

@acer I've been learning this on the fly during my research, and a lot of the calculations do end up taking a lot of time because of the amount of numbers it crunches through. i.e., calculating eigenvectors of 500x500 matrices. My introduction to Maple was my advisor emailing me a worksheet and having me execute it. I've surpassed his knowledge on some facets of Maple, but if I haven't had direct need of it to execute my research I'm still extremely naive when it comes to the program.

Basically....I kind of know what you mean, but what is 1D Maple Notation, and how is it different??

....Oh. I answered myself by playing around in Maple. Nevermind! It's the 'non-pretty' version, that's kind of like terminal, but not!

@Carl Love This rather confirms acer's conclusion about it being a 2D math parsing bug. I have a 3rd if statement within the procedure, not too much earlier than the one I'd mentioned in my larger post; that one had also given me trouble, but I was able to figure out how to put it into `if` form, and thus trouble was averted. I wasn't able to determine how to do the same with my more recent addition, since it has two commands in it. There appears to be some complication in this one procedure that's coming about from having two if....end if statements present. But if they're in `if` execution form, it's fine. 

This is all supporting my lab's conclusion that Maple is a 'chaotic neutral' program. 

Thanks for the example on how to rewrite it into `if` form!

@tomleslie Why did the the (n1,n2) -> if...then...elif...then....elif...then...else....end if: run fine before?


And the 'working' process was commented out so as to throw the error. However, prior to my adding the statement

if eval_size > 4 then Search(max(seq(eval_cont[i], i = 4 .. eval_size)), eval_cont); evals_pairlist := evals_pairlist[[1 .. 3, %]] end if

I had no need of the proc(n1,n2) line, as the (n1,n2) ->  line worked perfectly well. Thus, the question and post.  (And yes I know about those local variables, they were added recently and just as a check for some values, and they're going to go away just as soon.)


@acer I almost suspected as much, but the usual method of 'search for the \newline or \space that Maple isn't reading correctly' didn't pan out this time. And I don't particularly have the desire to go through even just the latter part of this procedure line by line trying to figure out what it's throwing a fit about now. Especially since my usual 'hard-fix' for such an issue of retyping whatever it was I'd pasted in didn't change anything.

Thank you for taking a look at it regardless.

@acer Here is the document, complete with error. As I'd mentioned, they are all encapsulated in a much larger process. Coupled_Frequency_8th.mw


There was no issue with the (n1,n2) procedure prior to my adding the second if-statement. But after I added it, I got the inline error. Then I rewrote the (n1,n2) procedure as detailed in the original post, and the inline error ceased. Which to me makes no sense as there is no difference in meaning to my mind.

Page 1 of 1