kopia lustrzana https://github.com/animator/learn-python
Merge branch 'main' into main
commit
807d0f3b41
|
@ -24,8 +24,8 @@ The list of topics for which we are looking for content are provided below along
|
|||
- Web Scrapping - [Link](https://github.com/animator/learn-python/tree/main/contrib/web-scrapping)
|
||||
- API Development - [Link](https://github.com/animator/learn-python/tree/main/contrib/api-development)
|
||||
- Data Structures & Algorithms - [Link](https://github.com/animator/learn-python/tree/main/contrib/ds-algorithms)
|
||||
- Python Mini Projects - [Link](https://github.com/animator/learn-python/tree/main/contrib/mini-projects)
|
||||
- Python Question Bank - [Link](https://github.com/animator/learn-python/tree/main/contrib/question-bank)
|
||||
- Python Mini Projects - [Link](https://github.com/animator/learn-python/tree/main/contrib/mini-projects) **(Not accepting)**
|
||||
- Python Question Bank - [Link](https://github.com/animator/learn-python/tree/main/contrib/question-bank) **(Not accepting)**
|
||||
|
||||
You can check out some content ideas below.
|
||||
|
||||
|
|
|
@ -0,0 +1,192 @@
|
|||
# Exception Handling in Python
|
||||
|
||||
Exception Handling is a way of managing the errors that may occur during a program execution. Python's exception handling mechanism has been designed to avoid the unexpected termination of the program, and offer to either regain control after an error or display a meaningful message to the user.
|
||||
|
||||
- **Error** - An error is a mistake or an incorrect result produced by a program. It can be a syntax error, a logical error, or a runtime error. Errors are typically fatal, meaning they prevent the program from continuing to execute.
|
||||
- **Exception** - An exception is an event that occurs during the execution of a program that disrupts the normal flow of instructions. Exceptions are typically unexpected and can be handled by the program to prevent it from crashing or terminating abnormally. It can be runtime, input/output or system exceptions. Exceptions are designed to be handled by the program, allowing it to recover from the error and continue executing.
|
||||
|
||||
## Python Built-in Exceptions
|
||||
|
||||
There are plenty of built-in exceptions in Python that are raised when a corresponding error occur.
|
||||
We can view all the built-in exceptions using the built-in `local()` function as follows:
|
||||
|
||||
```python
|
||||
print(dir(locals()['__builtins__']))
|
||||
```
|
||||
|
||||
|**S.No**|**Exception**|**Description**|
|
||||
|---|---|---|
|
||||
|1|SyntaxError|A syntax error occurs when the code we write violates the grammatical rules such as misspelled keywords, missing colon, mismatched parentheses etc.|
|
||||
|2|TypeError|A type error occurs when we try to perform an operation or use a function with objects that are of incompatible data types.|
|
||||
|3|NameError|A name error occurs when we try to use a variable, function, module or string without quotes that hasn't been defined or isn't used in a valid way.|
|
||||
|4|IndexError|A index error occurs when we try to access an element in a sequence (like a list, tuple or string) using an index that's outside the valid range of indices for that sequence.|
|
||||
|5|KeyError|A key error occurs when we try to access a key that doesn't exist in a dictionary. Attempting to retrieve a value using a non-existent key results this error.|
|
||||
|6|ValueError|A value error occurs when we provide an argument or value that's inappropriate for a specific operation or function such as doing mathematical operations with incompatible types (e.g., dividing a string by an integer.)|
|
||||
|7|AttributeError|An attribute error occurs when we try to access an attribute (like a variable or method) on an object that doesn't possess that attribute.|
|
||||
|8|IOError|An IO (Input/Output) error occurs when an operation involving file or device interaction fails. It signifies that there's an issue during communication between your program and the external system.|
|
||||
|9|ZeroDivisionError|A ZeroDivisionError occurs when we attempt to divide a number by zero. This operation is mathematically undefined, and Python raises this error to prevent nonsensical results.|
|
||||
|10|ImportError|An import error occurs when we try to use a module or library that Python can't find or import succesfully.|
|
||||
|
||||
## Try and Except Statement - Catching Exception
|
||||
|
||||
The `try-except` statement allows us to anticipate potential errors during program execution and define what actions to take when those errors occur. This prevents the program from crashing unexpectedly and makes it more robust.
|
||||
|
||||
Here's an example to explain this:
|
||||
|
||||
```python
|
||||
try:
|
||||
# Code that might raise an exception
|
||||
result = 10 / 0
|
||||
except:
|
||||
print("An error occured!")
|
||||
```
|
||||
|
||||
Output
|
||||
|
||||
```markdown
|
||||
An error occured!
|
||||
```
|
||||
|
||||
In this example, the `try` block contains the code that you suspect might raise an exception. Python attempts to execute the code within this block. If an exception occurs, Python jumps to the `except` block and executes the code within it.
|
||||
|
||||
## Specific Exception Handling
|
||||
|
||||
You can specify the type of expection you want to catch using the `except` keyword followed by the exception class name. You can also have multiple `except` blocks to handle different exception types.
|
||||
|
||||
Here's an example:
|
||||
|
||||
```python
|
||||
try:
|
||||
# Code that might raise ZeroDivisionError or NameError
|
||||
result = 10 / 0
|
||||
name = undefined_variable
|
||||
except ZeroDivisionError:
|
||||
print("Oops! You tried to divide by zero.")
|
||||
except NameError:
|
||||
print("There's a variable named 'undefined_variable' that hasn't been defined yet.")
|
||||
```
|
||||
|
||||
Output
|
||||
|
||||
```markdown
|
||||
Oops! You tried to divide by zero.
|
||||
```
|
||||
|
||||
If you comment on the line `result = 10 / 0`, then the output will be:
|
||||
|
||||
```markdown
|
||||
There's a variable named 'undefined_variable' that hasn't been defined yet.
|
||||
```
|
||||
|
||||
## Important Note
|
||||
|
||||
In this code, the `except` block are specific to each type of expection. If you want to catch both exceptions with a single `except` block, you can use of tuple of exceptions, like this:
|
||||
|
||||
```python
|
||||
try:
|
||||
# Code that might raise ZeroDivisionError or NameError
|
||||
result = 10 / 0
|
||||
name = undefined_variable
|
||||
except (ZeroDivisionError, NameError):
|
||||
print("An error occured!")
|
||||
```
|
||||
|
||||
Output
|
||||
|
||||
```markdown
|
||||
An error occured!
|
||||
```
|
||||
|
||||
## Try with Else Clause
|
||||
|
||||
The `else` clause in a Python `try-except` block provides a way to execute code only when the `try` block succeeds without raising any exceptions. It's like having a section of code that runs exclusively under the condition that no errors occur during the main operation in the `try` block.
|
||||
|
||||
Here's an example to understand this:
|
||||
|
||||
```python
|
||||
def calculate_average(numbers):
|
||||
if len(numbers) == 0: # Handle empty list case seperately (optional)
|
||||
return None
|
||||
try:
|
||||
total = sum(numbers)
|
||||
average = total / len(numbers)
|
||||
except ZeroDivisionError:
|
||||
print("Cannot calculate average for a list containing zero.")
|
||||
else:
|
||||
print("The average is:", average)
|
||||
return average #Optionally return the average here
|
||||
|
||||
# Example usage
|
||||
numbers = [10, 20, 30]
|
||||
result = calculate_average(numbers)
|
||||
|
||||
if result is not None: # Check if result is available (handles empty list case)
|
||||
print("Calculation succesfull!")
|
||||
```
|
||||
|
||||
Output
|
||||
|
||||
```markdown
|
||||
The average is: 20.0
|
||||
```
|
||||
|
||||
## Finally Keyword in Python
|
||||
|
||||
The `finally` keyword in Python is used within `try-except` statements to execute a block of code **always**, regardless of whether an exception occurs in the `try` block or not.
|
||||
|
||||
To understand this, let us take an example:
|
||||
|
||||
```python
|
||||
try:
|
||||
a = 10 // 0
|
||||
print(a)
|
||||
except ZeroDivisionError:
|
||||
print("Cannot be divided by zero.")
|
||||
finally:
|
||||
print("Program executed!")
|
||||
```
|
||||
|
||||
Output
|
||||
|
||||
```markdown
|
||||
Cannot be divided by zero.
|
||||
Program executed!
|
||||
```
|
||||
|
||||
## Raise Keyword in Python
|
||||
|
||||
In Python, raising an exception allows you to signal that an error condition has occured during your program's execution. The `raise` keyword is used to explicity raise an exception.
|
||||
|
||||
Let us take an example:
|
||||
|
||||
```python
|
||||
def divide(x, y):
|
||||
if y == 0:
|
||||
raise ZeroDivisionError("Can't divide by zero!") # Raise an exception with a message
|
||||
result = x / y
|
||||
return result
|
||||
|
||||
try:
|
||||
division_result = divide(10, 0)
|
||||
print("Result:", division_result)
|
||||
except ZeroDivisionError as e:
|
||||
print("An error occured:", e) # Handle the exception and print the message
|
||||
```
|
||||
|
||||
Output
|
||||
|
||||
```markdown
|
||||
An error occured: Can't divide by zero!
|
||||
```
|
||||
|
||||
## Advantages of Exception Handling
|
||||
|
||||
- **Improved Error Handling** - It allows you to gracefully handle unexpected situations that arise during program execution. Instead of crashing abruptly, you can define specific actions to take when exceptions occur, providing a smoother experience.
|
||||
- **Code Robustness** - Exception Handling helps you to write more resilient programs by anticipating potential issues and providing approriate responses.
|
||||
- **Enhanced Code Readability** - By seperating error handling logic from the core program flow, your code becomes more readable and easier to understand. The `try-except` blocks clearly indicate where potential errors might occur and how they'll be addressed.
|
||||
|
||||
## Disadvantages of Exception Handling
|
||||
|
||||
- **Hiding Logic Errors** - Relying solely on exception handling might mask underlying logic error in your code. It's essential to write clear and well-tested logic to minimize the need for excessive exception handling.
|
||||
- **Performance Overhead** - In some cases, using `try-except` blocks can introduce a slight performance overhead compared to code without exception handling. Howerer, this is usually negligible for most applications.
|
||||
- **Overuse of Exceptions** - Overusing exceptions for common errors or control flow can make code less readable and harder to maintain. It's important to use exceptions judiciously for unexpected situations.
|
|
@ -7,3 +7,4 @@
|
|||
- [Regular Expressions in Python](regular_expressions.md)
|
||||
- [JSON module](json-module.md)
|
||||
- [Map Function](map-function.md)
|
||||
- [Exception Handling in Python](exception-handling.md)
|
||||
|
|
|
@ -0,0 +1,71 @@
|
|||
# Grid Search
|
||||
|
||||
Grid Search is a hyperparameter tuning technique in Machine Learning that helps to find the best combination of hyperparameters for a given model. It works by defining a grid of hyperparameters and then training the model with all the possible combinations of hyperparameters to find the best performing set.
|
||||
|
||||
The Grid Search Method considers some hyperparameter combinations and selects the one returning a lower error score. This method is specifically useful when there are only some hyperparameters in order to optimize. However, it is outperformed by other weighted-random search methods when the Machine Learning model grows in complexity.
|
||||
|
||||
## Implementation
|
||||
|
||||
Before applying Grid Searching on any algorithm, data is divided into training and validation set, a validation set is used to validate the models. A model with all possible combinations of hyperparameters is tested on the validation set to choose the best combination.
|
||||
|
||||
Grid Searching can be applied to any hyperparameters algorithm whose performance can be improved by tuning hyperparameter. For example, we can apply grid searching on K-Nearest Neighbors by validating its performance on a set of values of K in it. Same thing we can do with Logistic Regression by using a set of values of learning rate to find the best learning rate at which Logistic Regression achieves the best accuracy.
|
||||
|
||||
Let us consider that the model accepts the below three parameters in the form of input:
|
||||
1. Number of hidden layers `[2, 4]`
|
||||
2. Number of neurons in every layer `[5, 10]`
|
||||
3. Number of epochs `[10, 50]`
|
||||
|
||||
If we want to try out two options for every parameter input (as specified in square brackets above), it estimates different combinations. For instance, one possible combination can be `[2, 5, 10]`. Finding such combinations manually would be a headache.
|
||||
|
||||
Now, suppose that we had ten different parameters as input, and we would like to try out five possible values for each and every parameter. It would need manual input from the programmer's end every time we like to alter the value of a parameter, re-execute the code, and keep a record of the outputs for every combination of the parameters.
|
||||
|
||||
Grid Search automates that process, as it accepts the possible value for every parameter and executes the code in order to try out each and every possible combination outputs the result for the combinations and outputs the combination having the best accuracy.
|
||||
|
||||
Higher values of C tell the model, the training data resembles real world information, place a greater weight on the training data. While lower values of C do the opposite.
|
||||
|
||||
## Explaination of the Code
|
||||
|
||||
The code provided performs hyperparameter tuning for a Logistic Regression model using a manual grid search approach. It evaluates the model's performance for different values of the regularization strength hyperparameter C on the Iris dataset.
|
||||
1. datasets from sklearn is imported to load the Iris dataset.
|
||||
2. LogisticRegression from sklearn.linear_model is imported to create and fit the logistic regression model.
|
||||
3. The Iris dataset is loaded, with X containing the features and y containing the target labels.
|
||||
4. A LogisticRegression model is instantiated with max_iter=10000 to ensure convergence during the fitting process, as the default maximum iterations (100) might not be sufficient.
|
||||
5. A list of different values for the regularization strength C is defined. The hyperparameter C controls the regularization strength, with smaller values specifying stronger regularization.
|
||||
6. An empty list scores is initialized to store the model's performance scores for different values of C.
|
||||
7. A for loop iterates over each value in the C list:
|
||||
8. logit.set_params(C=choice) sets the C parameter of the logistic regression model to the current value in the loop.
|
||||
9. logit.fit(X, y) fits the logistic regression model to the entire Iris dataset (this is typically done on training data in a real scenario, not the entire dataset).
|
||||
10. logit.score(X, y) calculates the accuracy of the fitted model on the dataset and appends this score to the scores list.
|
||||
11. After the loop, the scores list is printed, showing the accuracy for each value of C.
|
||||
|
||||
### Python Code
|
||||
|
||||
```python
|
||||
from sklearn import datasets
|
||||
from sklearn.linear_model import LogisticRegression
|
||||
|
||||
iris = datasets.load_iris()
|
||||
X = iris['data']
|
||||
y = iris['target']
|
||||
|
||||
logit = LogisticRegression(max_iter = 10000)
|
||||
|
||||
C = [0.25, 0.5, 0.75, 1, 1.25, 1.5, 1.75, 2]
|
||||
|
||||
scores = []
|
||||
for choice in C:
|
||||
logit.set_params(C=choice)
|
||||
logit.fit(X, y)
|
||||
scores.append(logit.score(X, y))
|
||||
print(scores)
|
||||
```
|
||||
|
||||
#### Results
|
||||
|
||||
```
|
||||
[0.9666666666666667, 0.9666666666666667, 0.9733333333333334, 0.9733333333333334, 0.98, 0.98, 0.9866666666666667, 0.9866666666666667]
|
||||
```
|
||||
|
||||
We can see that the lower values of `C` performed worse than the base parameter of `1`. However, as we increased the value of `C` to `1.75` the model experienced increased accuracy.
|
||||
|
||||
It seems that increasing `C` beyond this amount does not help increase model accuracy.
|
|
@ -11,3 +11,4 @@
|
|||
- [Types of optimizers](Types_of_optimizers.md)
|
||||
- [Logistic Regression](logistic-regression.md)
|
||||
- [Clustering](clustering.md)
|
||||
- [Grid Search](grid-search.md)
|
||||
|
|
Ładowanie…
Reference in New Issue