Christopher2222

5100 Reputation

24 Badges

11 years, 362 days

MaplePrimes Activity


These are replies submitted by Christopher2222

I believe someone changed it to a post because it had real relevance that maplesoft should address - after I saw it was changed I agreed it was a good thing to do. Not sure what happened to the other one.  The fact they both got erased is unfortunate.  I was going to respond to one of them but I can't exactly remember the context of the information.

Perhaps a maplesoft administrator can restore them.

alt-f4 works in 2019.0 in windows 7.

That's a good idea of point release updates, I never thought of that.  But don't other parts outside of Maple also get updated?  Could we say that it functions exactly the same as if the point release was done inside a virtual machine where it's completely separated from a superseeded release?

I'd give them a few weeks, or at least until the end of the year to come up with a fix.  The sooner the better from a marketing standpoint.

As a makeshift for future, does anyone know if (before an update) we could pull out certain files and stick them back in if the update happens to be filled with bugs?  Like for example some main files, and I'm not sure which ones but maybe maple.bin some .dll files etc.  So if the update is a failure we can at least roll back by just copying back and writing over the new files with the old ones.  I'm sure I'm missing something and it can't be done like that now-a-days but perhaps it can.  Or maybe Maple can put in a rollback option???

Sounds like some serious issues with the 2019.2 update that need immediate attention by maplesoft.

 

It's ok in 2019.0, check if the same happens in document mode.

I believe the best way to revert to 2019.1 is to uninstall 2019, re-install 2019.0 and update to 2019.1.  There may be a better way but when Maple updates I believe it overwrites the main files and doesn't back them up which makes rolling back to a previous edition not a quick task.

 

 

Turning data into sound is called sonification.  But it's not exactly what I think you are doing but I might understand what you are trying to do.  You want to create a waveform based on previous data. 

Let's see if I understand you correctly.  So, let's say we have some sample waveform described by (sorry I'm just snipping and pasting)


which is of course periodic and looks like this

... and what you're saying is suppose we have only data (no equations) from 0..2. so what we have is just:

You want to use that data to generate further lines of the wave ie. randomly selecting from the previous distribution of ups and downs whether the wave is to go up or down (I'm guessing that is what you meant when you said "know the direction of up and down") and also the lengths of how far it will go, again based on the previous data.  Sort of like a random walk picked from the distribution of user data. 

Am I right?

Sounds pretty neat.. no pun intended.  Shouldn't be too hard to complete in maple. 

Without the help of the graph I wouldn't quickly be able to notice there are 9 critical points (3 local maxima's, 3 local minima's and 3 saddle points).

In the Student[Calculus1] package there is a CriticalPoints command but it is currently limited to one variable. (Maple 2020 Wishlist?)

With our expression we need to use fsolve and provide a range (otherwise we either get "warning, solutions may have been lost" or just the original equations back unsolved)

fx:=simplify(diff(f(x,y),x):
fy:=simplify(diff(f(x,y),y):

fsolve({fx=0,fy=0},{x=-3..3,y=-3..3})

                    {x = -0.2659375568, y = 0.4667399937}

So there's one critical point.  Is there an easier way to find critical points without graphing?

Thank you Carl and Rouben. 

I think he wanted the gradplot displayed as solid lines since contour lines are already shown in the application.

Has anyone come up with anything?

@Kitonum It appears the code for the second part by Robert Israel doesn't show the full code.  I currently can't see how he gets the Raw ouputs.

@Carl Love I usually just cut them however I want.  Indeed the cutting is a little more difficult if you don't go all the way across but it doesn't matter for me, I would just cut close to the perpendicular point and then finish off with a hand saw.  Be neat to see both ways.  Which method would end up with a larger useable waste piece?  That is also of interest. 

In what context is the error related to?

Please post your example that caused the error.

@acap_619 What happens when you execute this line?  What is your output?

96*sin(2*beta*y)*cos(2*beta*y)*beta^4 + 96*sin(2*beta*y)*beta^4 ;

 

4 5 6 7 8 9 10 Last Page 6 of 139