## 5790 Reputation

15 years, 309 days

## No...

I'm pretty sure my earlier post got erased.  To summary the post that was there.  Someone will have to make a module in Maple to correct for lens distortion.  We will try to assist.  Can Maple do such a thing?

## Not exactly sure...

Tell you the truth I'm not exactly sure what happened there.  I was running a few memory intensive programs in the background and had to restart my system, it slowed right down, must have been a software issue.   I also can't seem to replicate what I did.

And thanks for the in depth explanations.

(edit add) - I may have figured it out.  On occasion I calculate without restart, the value .97 may have been in that location, it only makes sense.  However in the Browse, the Matrix it remains in a multiple '9' decimal form if I multiplied it by 4.  So either I strictly work in arrays and disregard the matrix in Browse or just live with it.  It would probably export with the etraneous 9's to excel ... wow, no it actually doesn't.

Again thanks for the inputs.

## so much for precision...

.97 and .98 get mapped to the exact same number

A single round of multiplication already introduces a roundoff error.

with(ImageTools):
img:=Create(20,20):
img[2,2]:=.98:

img[2,2];

.96999999999974

sorry if the digit isn't exactly but my point is ....

img[2,2]*4 = .98 * 4  #The answer should hold true

3.88  =  3.92

Sadly it does not.  So is this just the nature of how image tools handles the numbers or can it be fixed?

## rounding...

Yes, sorry I typed it in wrong and you have it correct.

So I'm understanding, if I carried out multiple operations on a .97 number in the image matrix, rounding errors won't be introduced.

## Maple changing numbers - serious?...

Maybe the initial title of the thread doesn't represent the seriousness of the issue.

Does anyone else get the same thing.  This looks like maple is approximating and replacing a number.  It shouldn't be.  For imageTools I suppose it's not that big of a deal but suppose I were to perform some mathematical operations on a matrix image for cryptographic purposes, if maple reports the wrong numbers the system would fail.

## Maple...

Maple has always been my favorite and my goto symbolic software of choice.  I'm pretty sure it was because it was the first one I purchased back in my University days Maple Vr3 and because I was studying at Waterloo, so it was sort of a pride thing and being able to support the software that originated out of the same University.  In any case I changed careers after I graduated and lost touch with Maple for a number of years and then only sparingly dabbled around with it when I could spare the time between family and the ever growing list of things that need to get done around the home.

I tried Matlab in 2004 but never really got into it (time restraints) but it never really impressed me at the time.  I didn't try Mathematica because I didn't see the need.  Maple had most of what I wanted, and I'd rather support a software company that was close to home, so you could say I was a bit biased, now it's owned by a Japanese company but I still root for Maple.  Also partly because it was so powerful and not many people knew about it.  So after reading the history of maple and the interview with one of it's co-founders, it sparked more of my interest in it.  It seemed they initially had the run on the field and then the competition, sort of, caught up.  Mathematica with it's fancy eye candy drew lots of people to purchase it, and Matlab with it's ability to crunch numbers.  Maple was there, it's ability to handle Mathematics with finesse had it's place in the market as well, albeit not a well known one but one none-the-less.  Granted Maple still has it's share of bugs and it's also realizing that eye-candy is now one of those must haves in mathematics nowadays, of course most of it's determined by the code that produces it but the easier the better.

Thanks for the link.  I would have never known about it otherwise.  I'm about to head over there and cast a vote.  I'm willing to bet that Maple's popularity has spread quite a bit over the last 4 years.  I've been seeing more articles related to Maple lately, good to see it happening but sad to see the uniqueness of it start to pass away.

## manipulate picture to text...

So you want to take the picture and map the positions of the black, white and open spaces to a grid (array) for further operations?

If Maple could detect a space, white or black stone then associate it with a general position in the grid (matrix), it looks like a fairly complex set of operations or procedures you are asking maple to perform.  I also wonder how that could be done.

## manipulate picture to text...

So you want to take the picture and map the positions of the black, white and open spaces to a grid (array) for further operations?

If Maple could detect a space, white or black stone then associate it with a general position in the grid (matrix), it looks like a fairly complex set of operations or procedures you are asking maple to perform.  I also wonder how that could be done.

## Cannot maximize window...

When you're finished manipulating the file you can just write it to a file to use in windows viewer or paint program or your favorite image manipulator.  Just use the write command:

Write("f:/test.bmp",img3);

Since the bmp I used was already pretty much black and white there was probably no reason to use the convert line in there, it would work without it.  Also the white space has turned gray when viewing the written bmp file in an image processor so you'll have to figure out a way to change the gray space to white space and then write it to a file for better results.  FitIntensity should do that trick:

img4 := FitIntensity(img3,0..1);

But you'll need to fine tune it.  Joe Riel has some better methods below.

No the window unfortunately can not be maximized.  I was actually going to put in a software request for that and if you zoom in yes, the scroll option should be available.

## Cannot maximize window...

When you're finished manipulating the file you can just write it to a file to use in windows viewer or paint program or your favorite image manipulator.  Just use the write command:

Write("f:/test.bmp",img3);

Since the bmp I used was already pretty much black and white there was probably no reason to use the convert line in there, it would work without it.  Also the white space has turned gray when viewing the written bmp file in an image processor so you'll have to figure out a way to change the gray space to white space and then write it to a file for better results.  FitIntensity should do that trick:

img4 := FitIntensity(img3,0..1);

But you'll need to fine tune it.  Joe Riel has some better methods below.

No the window unfortunately can not be maximized.  I was actually going to put in a software request for that and if you zoom in yes, the scroll option should be available.

## modification...

Okay, yes modifying the elements is what I was referring to.  So large lists become doubly larger each time you modify them hence eroding your memory.  I'm so used to using lists I've become accustomed to it instead of using arrays where I should, for that I must modify my mindset and change my old habbits.

## Tieing up a small error...

The Maple12 section is linked to Maple11.pdf .  There's no real change between the two documents except the title.  However if you wish the proper link just rename 11 in the address bar to 12 to get the proper link.

## survival of the business...

So it appears that working on older versions that are no longer supported could drive a software company into the ground.  However given the current economic times people may not want to or can not afford any currently available versions of maple to play around with or work on.

If older versions were still available for a small fraction of the cost, in fact just making them available to buy shouldn't cost the company too much money if they were to use an on demand type of sales system.  That would keep overhead to a minimum.

Supporting the bug issue is a different matter since offering patches or updates would cost a considerable amount of resources.  Maybe new maplesoft employees could begin their training at the company by fixing bugs in older versions during their first months of training.  It wouldn't provide any immediate feedback for the company but at the same time it would familiarize them with the maple environment and get them problem solving right away.  Of course it may not work at all.

The business has to please the customers, but they also have to make a profit.  Opening up the market and selling older versions again might offer a window of opportunity for the company to make bug fixes but may also hold the company back from it's full potential on newer projects.

## Older version support - have Maple offer...

After thinking a little you're probably right, and thanks for those interesting links.  But how much could it hurt a company to deligate a small amount of resources into finding bugs.  Of course the user base for Maple 4.0 is probably almost nearly zero if already isn't.  Consider microsoft still supporting XP or Win 95 for that matter, their clientelle would be incredibly huge, not that it already isn't, but the fact that they dropped support for older versions caused a lot of followers to stray (to MAC?  i don't know)  then again it's a drain on the resources and most likely doesn't make any money at all for the company from a business perspective.

Being in a brainstorming mood, I'd like to wonder if Maple opted to sell older versions of it's platform for say ... \$10 for Maple V ... or say \$50 for Maple 6  etc... I don't know, I was just making up numbers but it would allow someone who wouldn't normally buy Maple to spend a few dollars to try out an old version.  They could have some sort of pricing formula so that their older products could still make them money and at the same time use that money to refine those older versions.  The older versions are still quite useful in some respects.

Just a thought.  Maybe maplesoft will put some thought into it?

## SCR submitted a while ago on this...

I submitted an SCR regarding this exact issue a while ago on June 16, 2009.  Regarding the Round screen display option.

It appears it has not been fixed in the new updates.

 First 146 147 148 149 150 151 152 Page 148 of 155
﻿