◆ MATLAB

Locate extrema using Live Editor

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All MATLAB tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need to find the maximum and minimum values in the 'temperature_data.mat' file. Load the…+
I need to find the maximum and minimum values in the 'temperature_data.mat' file. Load the data, identify the peak and trough for the 'sensor_readings' variable, and display them clearly in the Live Editor output. Make sure the script runs without errors.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I present these sensor readings to the design review committee, help me make the extrema…+
Before I present these sensor readings to the design review committee, help me make the extrema analysis more robust. Besides just finding the max and min, highlight any points that fall outside two standard deviations from the mean, and add a visual marker on the plot for these outliers. This will make it easier for the team to spot anomalies quickly.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just ran the live script for the new vibration sensor data, and the extrema values are wildly…+
I just ran the live script for the new vibration sensor data, and the extrema values are wildly different from last week's, even though the test conditions were identical.
I just ran the live script for the new vibration sensor data, and the extrema values are wildly different from last week's, even though the test conditions were identical. I'm afraid I've either made a mistake in the data loading or the sensor itself is faulty, but I can't tell which. The project lead needs an explanation by end of day. What's the most likely cause for such a drastic shift, and what's the fastest way to check if it's a data processing error or a sensor issue?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time manually re-running extrema analysis on new datasets from different sensors,…+
I keep losing time manually re-running extrema analysis on new datasets from different sensors, and often forget to update the plot titles or labels for each one.
I keep losing time manually re-running extrema analysis on new datasets from different sensors, and often forget to update the plot titles or labels for each one. This leads to inconsistent reports and extra work fixing them later. What habit should I change to ensure my extrema analysis scripts automatically adapt to new data sources and consistently generate properly labeled plots without me having to remember every detail?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from MATLAB's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.