Im trying to plot, lifetime as a funct. of doping, and abs. coefficient as a function of wavelength. I've looked up some videos and good instructions from this Solved: How to produce a log based range variable or plot ... - PTC Community but I have a problem getting the plot to show while defining the range correctly, ie, units for the start and stop, adding steps. I can pull it up with python but not with Mathcad and I can't find out why. thank you,
Thank you,
ACCEPTED SOLUTION
Accepted Solutions
It would be a good idea to make the function QE_emit work OK with a single scalar value of lambda (without any vectorization). Once you have tested that function, you can call it vectorized with vector argument(s).
What I noticed so far:
When you write a(lambda) Prime assumes a function a, which does not exist. If you meant a * lambda you would have to explicitly write is a multiplication. So you would write e.g.
but I still wonder as you defined x being zero, so this expression would always be constant 1
As you now multiply by a (which has unit 1/m), there is again a unit mismatch because now the exponent again is not dimensionless but has the unit meter.
You could make x dimensionless again, but you would run into problems with the sinh and cosh function. Their argument must be dimensionless, too, and as Ln is a length, xj must be a length, too.
Further unit mismatches in the expressions
and
where one summand is dimensionless while the other is a length.
So you have to fix the unit mismatches in your formula first, then set up the function in a way that it works for a single argument lambda and the n you should be able to call it with vector arguments.
P.S.: Guess we again are far away from the thread topic "Range Plot with Logspace and Units "
Just answered your question in the old thread before I saw your new one here 😉
See Solved: Re: Circuit ODE set up and solution - symmetrical ... - PTC Community
I found that 100 points would suffice for a decent plot. The way you had used logspace would only create 70 points which may be a bit too coarse. Stuart increased to 1400 points 😉
BTW, while its not necessary to use vectorization because X^2 is an operation not defined for vectors and so Prime would apply automatic implicit vectorization, I would nonetheless suggest to use explicit vectorization on f(X). Just good habit IMHO and it avoids unexpected results if some day you define a function differently. You see the difference if you replace X^2 by X*X 🙂
Wider, as in increasing horizontally. It take a considerable amount of my day to scroll to the side bar, pass it and go to the next screen, slow down and come back hoping this time I can grab it, doing this about hundred times for each assignment. Also, when I'm screen sharing going over it with someone else, It becomes embarrassing too. If its a worksheet I'm referencing, I can set it on the rightmost screen, that way the mount curser can't pass the bar, it stops and then I can grab it easier, but the primary worksheet is always on one of middle screens so I can look at them straight for a long time. So the problem is stopping right when I can grab it, after that it can easily be moved with the mouse.
This screen shot is barely 2/3 of the screen, doesn't the side bar seem almost one dimensional? I think I have developed a PTSD towards it. First and second knuckles if right hand index finger hurts when I even talk about it. I've had a paid student version for at least three years and every year I pay for updated version. That doesn't count as a fully paid license? Thanks.
A
@cadtelsim wrote:
Wider, as in increasing horizontally. It take a considerable amount of my day to scroll to the side bar, pass it and go to the next screen, slow down and come back hoping this time I can grab it, doing this about hundred times for each assignment. Also, when I'm screen sharing going over it with someone else, It becomes embarrassing too. If its a worksheet I'm referencing, I can set it on the rightmost screen, that way the mount curser can't pass the bar, it stops and then I can grab it easier, but the primary worksheet is always on one of middle screens so I can look at them straight for a long time. So the problem is stopping right when I can grab it, after that it can easily be moved with the mouse.
This screen shot is barely 2/3 of the screen, doesn't the side bar seem almost one dimensional? I think I have developed a PTSD towards it. First and second knuckles if right hand index finger hurts when I even talk about it. I've had a paid student version for at least three years and every year I pay for updated version. That doesn't count as a fully paid license? Thanks.
Ah, it's the scroll bar you're talking about. I's misunderstood and thought you were referring to the advanced Slider control. 🙂
Yes, I agree with you. The window scroll bars can be tricky to find. Can you use the standard Windows keyboard shortcuts to move the screen to where you want?
From : https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/scrollbar_role
Keyboard scrolling must also be supported. When focus is within the viewport controlled by a scrollbar, the Up Arrow and Down Arrow (or Left Arrow and Right Arrow for a horizontal scroll bar) should move the scroll bar thumb proportionally. Additionally, the Page Up, Page Down, Space, and Shift + Space keys must move the content and the scroll thumb the height (or width) of the viewport for each key press until the bottom or top (or left or right) of the content is in view.
I can't, however, find a keyboard shortcut that reliably moves to the top or bottom of a worksheet using my Dell laptop keyboard (no numeric keypad).
Then there's the official Microsoft page:
Complaints about the scroll bar narrowness seem to have increased with the move from Windows 10 to Windows 11. Some people find that going to Accessibility in Settings and setting the scroll bars to Always On widens them a little bit, but I didn't see any effect on my laptop (which has a 4K screen).
See https://github.com/microsoft/terminal/issues/12395 for a discussion about the matter in the MS Terminal GUI. Apparently, all will be resolved when XAML gets fully implemented ...
https://github.com/microsoft/microsoft-ui-xaml/discussions
If you're brave (and I'm a natural-born coward) you could try the advice given here:
But I'll leave playing with the Registry to the adventurous, those who know what they're doing, or those who exist at the wrong point of the Dunning-Kruger model. (I've played with the Registry a lot, but doing so always makes me nervous)
Here's a screenshot of my Registry Editor with the scroll bar width changed from the default -255 to a wider -360 (15*n pixels wide). Maybe a small effect on the width (after restarting). However, if you're not an administrator on your PC, you might not be able to change Registry settings.
Stuart
Explore the GitHub Discussions forum for microsoft microsoft-ui-xaml. Discuss code, ask questions & collaborate with the developer community.
The vertical scroll bar was sufficiently narrow so as to make it difficult to use. And, IIRC, someone recently asked about making it wider (I'll second that, a little late). In 1.13.10336.0 it's even narrower than it was previously. Thin...
The vertical scroll bar was sufficiently narrow so as to make it difficult to use. And, IIRC, someone recently asked about making it wider (I'll second that, a little late). In 1.13.10336.0 it's even narrower than it was previously. Thin...
This is a full screen width (1916 pixels wide, I only lost 4 pixels at the window borders of Prime.
I have no problem using the scroll bars.
Now if you have a 4k display on a 15"screen, that may be a different story. In that case you could consider setting the display scale in windows to a value higher than 100%.
Success!
Luc
Thank you for clean plot, finally got that one plot. I'll work more on a vs lambda that doesn't show,
would you please see what I'm missing in the efficiency formula? I tried to simplify it but it still gave me an error.
Select each axis express and then press "Logarithmic Scaling" for both axis on the "Plot" ribbon.
Then delete the last value (10^10 which you seem to have typed in manually) on the x-axis to let Prime choose the appropriate value automatically.
EDIT: I just noticed that you edited your posting and deleted your question about your plot not showing what you expect, which is why I formulated this answer
According the function QE_emit:
1) Its not a fault but its noticable that the argument lambda is not used in the expression. So the result would be the same for any input argument lambda - constant function.
2) the error stems from the expression e^(-a*xj) because the exponent must be unit-less. a is of dimension length^-1, so xj must be of dimension length. You have to add the unit meter even if the value is zero!
Not sure if the single scalar result is what you expected. Maybe you should vectorize the whole right hand side of the function definition, not sure though.
It would be a good idea to make the function QE_emit work OK with a single scalar value of lambda (without any vectorization). Once you have tested that function, you can call it vectorized with vector argument(s).
What I noticed so far:
When you write a(lambda) Prime assumes a function a, which does not exist. If you meant a * lambda you would have to explicitly write is a multiplication. So you would write e.g.
but I still wonder as you defined x being zero, so this expression would always be constant 1
As you now multiply by a (which has unit 1/m), there is again a unit mismatch because now the exponent again is not dimensionless but has the unit meter.
You could make x dimensionless again, but you would run into problems with the sinh and cosh function. Their argument must be dimensionless, too, and as Ln is a length, xj must be a length, too.
Further unit mismatches in the expressions
and
where one summand is dimensionless while the other is a length.
So you have to fix the unit mismatches in your formula first, then set up the function in a way that it works for a single argument lambda and the n you should be able to call it with vector arguments.
P.S.: Guess we again are far away from the thread topic "Range Plot with Logspace and Units "
