Scientific inference skill

[prof Neuro mg T]

Homework Statement

Science

Relevant Equations

Inference skill

Please give explanation for scientific inference skill pdf, i wants to deep learn that..
Thank you

 

[berkeman]

Homework Statement: Science
Relevant Equations: Inference skill

Please give explanation for scientific inference skill pdf, i wants to deep learn that..
Thank you

Welcome to PF.

Can you please say more about your question? What do you mean by "pdf"? Have you tried doing a Google search on scientific inference skill?

 

[berkeman]

Have you tried doing a Google search on scientific inference skill?

For example, here are the search results when I do that search. Do these hits help?

https://www.google.com/search?client=firefox-b-1-d&q=scientific+inference+skill+pdf

 

[Barbarian]

Scientific inference skills encompass the ability to draw logical conclusions based on observations, evidence, and prior knowledge. There is Inductive inference. It istarts with observation and leads to broader generalizations or theories. The Deductive inferernce begins with hypothesis and then the experiment to test the theory.
That means that inductive method goes from specific case to general one and the deductive method is vice versa.
In my opinion, it is the skill that you can only learn with a lot of practice. When writing your conclusion you should preoritize describing what you saw during the experiment. In both methods I mentioned earlier you must tell what are the conditions of the experiment, why you choose one theory and not the other one and so on

 

[jbriggs444]

The "scientific inference skill" is nothing magical. Lots of people practice it every day. I spent a career using it and I have never been a practicing scientist.

An auto mechanic uses the skill when diagnosing a problem with your car. The customer reports a symptom. The mechanic may observe the car looking for further symptoms. He comes up with a list of hypotheses for conditions that could explain the symptoms. He runs tests to confirm or rule out various hypotheses. That is scientific inference in action. Theory is the part where you come up with hypotheses. Experiment is the part where you choose which tests to run and run them.

A programmer uses the skill when troubleshooting code. The program runs slow or produces the wrong result. Perhaps it does so intermittently. The programmer comes up with hypotheses about where the fault lies. Maybe in module A. Maybe in subroutine B. He constructs test cases, inserts debugging code or fires up the code debugger to further identify the problem.

An office worker uses the skill when trying to figure out who is stealing lunch on alternate Tuesdays. He comes up with hypotheses about the guilty party. Maybe he runs an experiment with copious quantities of Ex-Lax, ghost peppers or glow in the dark fingerprint dust.

I often used the skill in network engineering. Some application is running slow. How does the application work? This can be surprisingly difficult because end users and even application owners tend not to know how their applications work or even what servers they are using. How can we find out how the application works? Can we catch the problem in action? What bottlenecks could exist on the network? How can we test for them? Do the test results explain the observed symptoms? How can we mitigate or work around the issue? At almost every step in the process, one has hypotheses and testing.