Skip to content
Snippets Groups Projects
Commit 8661a2d7 authored by mathias.catala's avatar mathias.catala
Browse files

yes

parent 9c2c769d
No related branches found
No related tags found
No related merge requests found
CC = gcc
CFLAGS = -Wall -Wextra -std=c11
TARGET = matrix
SRCS = matrix.c
OBJS = $(SRCS:.c=.o)
$(TARGET): $(OBJS)
$(CC) $(CFLAGS) -o $@ $^
%.o: %.c
$(CC) $(CFLAGS) -c -o $@ $<
clean:
rm -f $(OBJS) $(TARGET)
# traitement_imagea
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin https://gitedu.hesge.ch/mathias.catala/traitement_imagea.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://gitedu.hesge.ch/mathias.catala/traitement_imagea/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
Source diff could not be displayed: it is too large. Options to address this: view the blob.
File added
#include "matrix.h"
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
error_code matrix_alloc(matrix *mat, int m, int n){
if (m <= 0 || n <= 0) {
return err;
}
mat->m = m;
mat->n = n;
// Allocate memory for the data array
mat->data = (int **)malloc(m * sizeof(int *));
if (mat->data == NULL) {
return err; // Memory allocation failed
}
// Allocate memory for each row of the matrix
for (int i = 0; i < m; i++) {
mat->data[i] = (int *)malloc(n * sizeof(int));
if (mat->data[i] == NULL) {
// If memory allocation fails, free previously allocated memory
for (int j = 0; j < i; j++) {
free(mat->data[j]);
}
free(mat->data);
return err; // Memory allocation failed
}
}
return ok; // Success
}
error_code matrix_init(matrix *mat, int m, int n, int val){
error_code alloc_result = matrix_alloc(mat, m, n);
if (alloc_result == err) {
return err; // Memory allocation failed
}
for (int i = 0; i < m; i++) {
for (int j = 0; j < n; j++) { // Corrected the condition i < m to j < n
mat->data[i][j] = val;
}
}
return ok;
}
error_code matrix_destroy(matrix *mat){
if (mat->data != NULL) {
// Free memory for each row
for (int i = 0; i < mat->m; i++) {
free(mat->data[i]);
}
// Free memory for row pointers
free(mat->data);
// Reset matrix fields
mat->data = NULL;
}
// Reset matrix dimensions
mat->m = -1;
mat->n = -1;
return ok;
}
error_code matrix_init_from_array(matrix *mat, int m, int n,int* data)
{
// Allouer de la mémoire pour le tableau 2D de la matrice
mat->data = (int **)malloc(m * sizeof(int *));
// Allouer de la mémoire pour chaque ligne de la matrice
for (int i = 0; i < m; i++) {
mat->data[i] = (int *)malloc(n * sizeof(int));
if (mat->data[i] == NULL) {
// Si l'allocation mémoire échoue, libérer la mémoire précédemment allouée
for (int j = 0; j < i; j++) {
free(mat->data[j]);
}
free(mat->data);
return err; // Erreur : échec de l'allocation mémoire
}
}
// Copier les données du tableau dans la matrice
for (int i = 0; i < m; i++) {
for (int j = 0; j < n; j++) {
mat->data[i][j] = data[i * n + j];
}
}
// Définir les dimensions de la matrice
mat->m = m;
mat->n = n;
return ok;
}
error_code matrix_clone(matrix *cloned, matrix mat){
cloned->data = (int **)malloc(mat.m * sizeof(int *));
for (int i = 0; i < mat.m; i++) {
cloned->data[i] = (int *)malloc(mat.n * sizeof(int));
if (cloned->data[i] == NULL) {
// Si l'allocation mémoire échoue, libérer la mémoire précédemment allouée
for (int j = 0; j < i; j++) {
free(cloned->data[j]);
}
free(cloned->data);
return err;
}
}
for (int i = 0; i < mat.m; i++) {
for(int j=0 ;j< mat.n;i++){
cloned->data[i][j]= mat.data[i][j];
}
}
cloned->m= mat.m;
cloned->n = mat.n;
return ok;
}
error_code matrix_print(matrix mat) {
for (int i = 0; i< mat.m; i++){
for (int j = 0 ; i< mat.n; j++ ){
printf("%d ",mat.data[i][j]);
}
}
return ok;
}
error_code matrix_get(int *elem, matrix mat,int ix, int iy){
// Vérifier si les indices ix et iy sont valides
if (ix < 0 || ix >= mat.m || iy < 0 || iy >= mat.n) {
return err; // Erreur : dépassement de capacité
}
// Récupérer l'élément de la matrice
*elem = mat.data[ix][iy];
return ok; // Succès
}
error_code matrix_set(matrix mat, int ix, int iy, int elem){
// Vérifier si les indices ix et iy sont valides
if (ix < 0 || ix >= mat.m || iy < 0 || iy >= mat.n) {
return err; // Erreur : dépassement de capacité
}
mat.data[ix][iy]= elem;
return ok;
}
error_code pgm_read_from_file(pgm *p, char *filename) {
// Open the file in read mode
FILE *file = fopen(filename, "r");
if (file == NULL) {
return err; // Error: failed to open file
}
// Buffer for reading lines from the file
char buffer[256];
// Read the first line containing PGM magic number
fgets(buffer, sizeof(buffer), file);
// Read the next line containing image width, height, and maximum gray value
int width, height, max_gray;
fscanf(file, "%d %d %d", &width, &height, &max_gray);
// Allocate memory for the pixel matrix
error_code alloc_result = matrix_alloc(&p->pixels, height, width);
if (alloc_result != ok) {
fclose(file);
return alloc_result; // Memory allocation failed
}
// Read pixel values
for (int i = 0; i < height; i++) {
for (int j = 0; j < width; j++) {
fscanf(file, "%d", &p->pixels.data[i][j]);
}
}
// Close the file
fclose(file);
// Initialize max value in the pgm structure
p->max = max_gray;
return ok; // Success
}
int main() {
// Create a pgm structure
pgm image;
// Read the PGM file
error_code result = pgm_read_from_file(&image, "mandrill.pgm");
// Check for errors
if (result != ok) {
printf("Error reading PGM file. Error code: %d\n", result);
return err;
}
// Print the image information
printf("Max value: %d\n", image.max);
printf("Image dimensions: %d x %d\n", image.pixels.m, image.pixels.n);
printf("Image data:\n");
for (int i = 0; i < image.pixels.m; i++) {
for (int j = 0; j < image.pixels.n; j++) {
printf("%d ", image.pixels.data[i][j]);
}
printf("\n");
}
// Free memory allocated for the image data
for (int i = 0; i < image.pixels.m; i++) {
free(image.pixels.data[i]);
}
free(image.pixels.data);
return 0;
}
typedef enum _error_code {
ok, err
} error_code;
typedef struct _matrix {
int m, n;
int ** data;
} matrix;
typedef struct _pgm {
int max;
matrix pixels;
} pgm;
// pGM functions
error_code pgm_read_from_file(pgm *p, char *filename);
error_code pgm_write_to_file(pgm *p, char *filename);
error_code pgm_negative(pgm *neg, pgm *orig);
error_code pgm_symmetry_hori(pgm *sym, pgm *orig);
//error_code pgm_crop(pgm *crop, pgm *orig,int32_t x0, int32_t x1, int32_t y0, int32_t y1);
// matrix functions
error_code matrix_alloc(matrix *mat, int m, int n);
error_code matrix_init(matrix *mat, int m, int n, int val);
error_code matrix_destroy(matrix *mat);
error_code matrix_init_from_array(matrix *mat, int m, int n,int* data);
error_code matrix_clone(matrix *cloned, matrix mat);
error_code matrix_print(matrix mat);
error_code matrix_get(int *elem, matrix mat, int ix, int iy);
error_code matrix_set(matrix mat, int ix, int iy, int elem);
// Read and write to files functions
\ No newline at end of file
File added
File added
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment