Blog

  • mx-check-deprecations

    Mendix Deprecation checker for widgets

    NPM DAVID npm version

    This tool is in beta

    It will check your .MPK (widget) files for possible Javascript deprecations that will break your widget in the new Mendix 6 release. Check the Mendix 6 client API, as well as the documented deprecations.

    Install

    Make sure you have the latest NodeJS LTS version installed. This should be 8.x.x

    Run:

    	npm install mx-check-deprecations -g

    This will install the checker globally.

    Usage

    Run it in your folder where you have widget (.mpk) files:

    	mx-check-deprecations

    Or check a single widget / list of widgets:

    	mx-check-deprecations WidgetFile.mpk WidgetFile2.mpk ...

    Further options

    	> mx-check-deprecations -h
    
      ================ Mendix Check Deprecations for Mendix ================
                                -- version 1.2.0 --
    
      Usage : mx-check-deprecations [OPTIONS] [<file.mpk> <file.mpk> <file.mpk> ... ]
    
      Either check individual files, or the whole folder
    
     Options:
       -d, --update-deprecations  Update the list with deprecations from Github (not implemented yet)
       -u, --update               Checks if there is an update for mx-check-deprecations
       -e, --excel                Output to Excel file : deprecations.xlsx
       -v, --verbose              Verbose output
       -s, --string               Search for a specific string
       -h, --help                 Shows this help screen
    
    

    License

    The MIT License (MIT)

    Copyright (c) 2015 Mendix

    Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

    The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

    THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

    Visit original content creator repository https://github.com/mendix/mx-check-deprecations
  • fastfeet.api

    FastFeet

    FastFeet API from Rocketseat GoStack

    ⚡ API to obtain the GoStack bootcamp certify

    GitHub language count Made by Léu Almeida License

    Introduction

    Fastfeet is a fictitious logistic company and this repository belong to the business logic and is the basis of a general structure and all of this be a part of the Rocketseat bootcamp certify. This API is based on Express for the overall structure, uses PostgreSQL for data storage, Redis for queue data control in conjunction with Bee-queue, and Sentry for error control and internal problem maintenance. Functions general features that use SMTP to trigger e-mails are done through nodemailer using express-handlebars and nodemailer-express-handlebars are kept in the src/app/views/emails folder.

    🔌 Prerequisites

    Quick Start

    First get all the requirements installed on your system. You will need to run the API using some Docker Images like PostgreSQL and Redis. Certified that do you have wall prerequisites, start the docker images dependencies:

    # Change the <password> below and on .env file to run PostgreSQL
    $ sudo docker run --name fastfeet -e POSTGRES_PASSWORD=<password> -p 5432:5432 -d postgres:11
    
    # Execute the Redis docker
    $ sudo docker run --name redisfastfeet -p 6379:6379 -d -t redis:alpine

    🔐 Getting started the API Restful backend

    Make a clone from the repo and install the dependencies

    # First of all, clone the project
    $ git clone https://github.com/LeuAlmeida/fastfeet.api.git
    
    # Enter in the DevRadar folder
    $ cd fastfeet.api
    
    # Install all dependencies using Yarn
    $ yarn

    Certify yourself that all environments are correct

    # Copy the .env folder
    $ cp .env.example .env
    
    # Insert your environments into .env file
    $ nano .env
    

    Prepare the PostgreSQL database

    # Migrate the database
    $ yarn sequelize db:migrate
    
    # Run the seeds
    $ yarn sequelize db:seed:all

    Start the project

    # Run the development server
    $ yarn dev
    
    # Case the output appears like this, is all ok
    yarn run v1.19.1
    $ nodemon src/server.js
    [nodemon] 2.0.2
    [nodemon] to restart at any time, enter `rs`
    [nodemon] watching dir(s): *.*
    [nodemon] watching extensions: js,mjs,json
    [nodemon] starting `node -r sucrase/register src/server.js`
    
    # The backend will run on port 3333
    # https://localhost:3333

    In a separated terminal, run the queue

    # Run the queue to enable mails and dependencies that uses bee-queue
    $ yarn queue
    
    # Case the output appears like this, is all ok
    yarn run v1.19.1
    $ nodemon src/queue.js
    [nodemon] 2.0.2
    [nodemon] to restart at any time, enter `rs`
    [nodemon] watching dir(s): *.*
    [nodemon] watching extensions: js,mjs,json
    [nodemon] starting `node -r sucrase/register src/queue.js`

    Routes

    You can learn more about the Routes, or you can see the own file.

    Demo

    Live demo incoming.

    ✔️ Stack

    Dependencies Security and Prevent errors
    Nodemon Bcrypt
    Bee-queue Dotenv
    Express Handlebars Express-async-errors
    Pg and pg-hstore JWT
    Sequelize Sentry
    Youch
    Yup

    ©️ License

    MIT License.

    See LICENSE for details.


    Visit original content creator repository https://github.com/LeuAlmeida/fastfeet.api
  • advanced-computer-graphics

    advanced-computer-graphics

    Homeworks for Advanced computer graphics, FRI 2022.

    1st homework: Scattered data interpolation

    Inverse distance weighting (IDW) with its basic form, the Shepard’s method and Modified Shepard’s method with limited radius of influence of each data point. Interpolate.exe reads standard input data (Console.ReadLine) and outputs floats to binary file output.raw. There is also an option to output byte binary file for visualization of the volume.

    Compile c# with:

    csc *.cs

    Run interpolate.exe with basic method (command prompt, not powershell):

    ./interpolate < input1k.txt --method basic --p 2 --min-x -1.5 --min-y -1.5 --min-z -1  --max-x 1.5 --max-y 1.5 --max-z 1  --res-x 128 --res-y 128 --res-z 64

    or modified method:

    ./interpolate < input1k.txt --method modified --r 0.5 --min-x -1.5 --min-y -1.5 --min-z -1  --max-x 1.5 --max-y 1.5 --max-z 1  --res-x 128 --res-y 128 --res-z 64

    2nd homework: Path tracing

    Physically based rendering path tracing framework with basic path tracing algorithm with Russian roulette for stopping and importance sampling of choosing ray directions, support for spherical light sources and Oren-Nayar material.

    Visit original content creator repository https://github.com/timkriz/advanced-computer-graphics
  • yeelight-shell-scripts

    Yeelight Shell Scripts

    Control Xiaomi Mi Yeelight (RGB) with shell scripts. Should work under any recent Linux with a bash or zsh – sorry, don’t know if that works under Windows/CygWin or Macos – you might need to rewrite the last line in the yeelight.sh script (e.g. by pipeing the output to netcat).

    License

    Copyright [2016] [Heinz Peter Hippenstiel]

    Licensed under the Apache License, Version 2.0 (the “License”); you may not use the files in this repository except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
    Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

    Setup

    You need to connect the light using the Yeelight app (or using any other appropriate way) to your network. Then enable Developer Mode (or LAN Control Mode in the current version of the app) for the light. This setting may need to be reset after a firmware update. You should also make sure that your DHCP server always assigns the same IP address to the light.

    Now edit the yeelight-ips file and enter the IP address of each light you have, separated by a space.

    Running

    Each of the yeelight-*.sh scripts has a specific function that is hopefully quite easy to guess from it’s name. All the scripts call the yeelight.sh script that really does the job. Each script requires several parameters – calling them without any will give you a usage prompt. All scripts require the ID of a light – this is the position of the light you entered in the setup part. The first light has the ID 0.

    Examples

    Switch on (to last used values)

    ./yeelight-scene.sh 0 On

    Switch on using 4300 Kelvin

    ./yeelight-scene.sh 0 4300

    Switch on Rainbow

    ./yeelight-scene.sh 0 Rainbow

    Switch on Disco

    ./yeelight-scene.sh 0 Disco

    Switch on Disco with 120ms

    DISCOSPEED=120 ./yeelight-scene.sh 0 Disco

    Set brightness to 50%

    ./yeelight-brightness.sh 0 50

    Set RGB color to BLUE (using absolut number, decimal and hex triples)

    ./yeelight-rgb.sh 0 255
    ./yeelight-rgb.sh 0 0,0,255
    ./yeelight-rgb.sh 0 x0,0,ff

    Set hue (hsv) to 32 (yellow) with 80% brightness (of that color – 0 means full white)

    ./yeelight-hue.sh 0 32 80

    Set color temperature to 6500 Kelvin

    ./yeelight-colortemp.sh 0 6500

    Integration with redshift

    yeelight-redshift.sh is a script that allows your lamp to change color temperature simultaneously with your monitor if you use redshift. Just like redshift, this script eases strain on your eyes if you use your computer at night. To use this script you need to copy ./samples/yeelight-redshift.timer and ./samples/yeelight-redshift.service to /etc/systemd/system/, change scrip location in yeelight-redshift.service. Then run sudo systemctl daemon-reload, sudo systemctlt enable yeelight-redshift.timer, sudo systemctl start yeelight-redshift.timer.

    You can also change some values in yeelight-redshift.sh if you need warmer color.

    For the script to work you need to have redshift installed.

    Contributed by Maxim Mishukov

    HA-Bridge and Amazon Alexa

    I am personally using this scripts on a Synology NAS with a running HA-Bridge.
    Since the scripts don’t require any additional tool or access rights you can just execute them directly from the HA-Bridge.
    Make sure the scripts are executable (chmod +x *.sh) and either you are using the full path or put them somewhere inside $PATH, for example /usr/local/bin/.

    I have setup different scenes as devices for the same light. There is a bedroom device which can be switched on/off and use the dim feature – this is just a normal setup. And there is also a sleep and a rainbow device that addresses the same light to apply this scenes.

    yeelight-disco.sh is a wrapper that only accepts one value – I use ${intensity.percent} from HA-Bridge. There is some math done with that value to fit into the 2-99% range (Strange: I can’t tell Alexa to use 1 or 100%) and still have some ‘disco-speed’. Adjust to your needs.

    Visit original content creator repository
    https://github.com/darth-hp/yeelight-shell-scripts

  • CSharpECSComparison

    What is this?

    This is a rough comparison table of all the “popular” ECS frameworks written and used in C#.

    Table

    Support…
    ✔️ = Full
    ✔️Ex = Full with extension
    = Partial
    = None

    Feature Leo
    ECS
    Leo
    EcsLite
    Default
    Ecs
    Svelto
    .ECS
    Morpeh Unity
    ECS
    Entitas chrome
    alex
    /ecs
    Nano
    ECS
    Ego
    CS
    actors
    .unity
    Feature
    Archetype based ✔️ ✔️ ✔️? ❌? Archetype based
    Filter/Query operations Has/Not
    (Inc/Exc)
    Has/Not
    (Inc/Exc)
    Has/Not
    Or/Nor
    Has/Not
    (With/
    Without)
    Has/Not/Or
    (All/Any/None)
    Has/Not, Any
    (All/None)
    Has/Not, Any Has/Not
    (With/
    Without)
    Has Has Filter/Query operations
    Components Type support struct struct struct
    /class
    /interface
    struct
    /interface
    struct struct
    /class
    class struct class class class? Components Type support
    Code Generation based ✔️ ✔️ ✔️ Code Generation based
    Dependencies None None None None ➖Unity
    Odin Inspector
    Unity ➖Unity Unity Unity Unity Unity Dependencies
    Engine agnostic ✔️ ✔️ ❌? ✔️ ✔️ Engine agnostic
    Custom Engine Support ✔️ ✔️ ✔️ ✔️ Custom Engine Support
    Threading support ✔️Ex ✔️Ex ✔️ ➖? ❌? ➖? Threading support
    World Events/Messages ✔️ ✔️ ✔️ ✔️ ❌? ❌? ✔️ ✔️ World Events/Messages
    One-Frame Components ✔️ ✔️ ✔️EX ❌? ✔️ One-Frame Components
    Dependency Injection
    Support
    ✔️ ✔️ Dependency Injection
    Support
    Shared Resource ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ Shared Resource
    Thread-safe ❌? ❌? Thread-safe
    Reactive System ✔️ ❌? ✔️ ✔️ ✔️ Reactive System
    Multiple components of same type on entity Multiple components of same type on entity
    Components can live without entities ✔️ ✔️ Components can live without entities
    Entities can live without components ✔️ ✔️ Entities can live without components
    Unity Editor View support ✔️Ex ✔️Ex ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ ✔️ Unity Editor View support
    Unity Editor Full Integration* ➖? ❌(WIP) ✔️ ✔️ ✔️? Unity Editor Full Integration*
    Unity Burst Compatible ✔️Ex ✔️ ✔️ ✔️ ❌? ❌? Unity Burst Compatible
    Unity Jobs Compatible ✔️Ex ✔️ ✔️ ✔️ ❌? ❌? ➖? Unity Jobs Compatible
    License MIT MIT MIT-0 MIT MIT Unity
    Companion
    License
    MIT MIT MIT MIT MIT License
    Last Major Version Release Date Feb
    2022
    Feb
    2022
    Feb
    2022
    May
    2023
    May
    2023
    Sep
    2022
    Sep
    2022
    Sep
    2020?
    Dec
    2019
    Mar
    2017
    Jul
    2020
    Last Major Version Release Date
    Feature Leo
    ECS
    Leo
    EcsLite
    Default
    Ecs
    Svelto
    .ECS
    Morpeh Unity
    ECS
    Entitas chrome
    alex
    /ecs
    Nano
    ECS
    Ego
    CS
    actors
    .unity
    Feature

    *(Unity Editor) Full Integration means that systems & components can be made, disabled, enabled, and configured in Unity Editor.

    How can I contribute?

    Find a table cell (or multiple) that isn’t filled out, and make an issue/pull request about it. While stating why it’s true (explanation doesn’t have to be very sophisticated or sourced/grounded, most of the time).
    OR
    Find a table cell (or multiple) that has a quesiton mark, and source why it’s true/untrue with an issue or pull request.

    FAQ

    Q: Why not split the table?
    A: I think the table isn’t big enough for a split to be valuable, and it’s easier to check for all the features you’d want with one glance, instead of going back and forth between two tables.

    Q: xECS isn’t here, why’s that?
    A: Idk, ask about it in a new issue, it might be too niche, or something.

    Visit original content creator repository
    https://github.com/Chillu1/CSharpECSComparison

  • predix-hello-scala

    Predix-Hello-Scala

    A basic attempt to develop on Predix.io using the Scala programming language and its ecosystem of awesome libraries.

    This sample app leverages on:

    What does it do?

    • Create a Finagle HTTP Server
    • Create a Finagle HTTP Client (based on this example) to call the Predix API Endpoint and get info on the environment
    • Show an extract from that info
      Cloud Foundry GE Open Sandbox: API version = 2.62.0

    Getting Started

    Install tools

    Be sure to have SBT installed on you machine

    Get the source code

    Make a directory for your project. Clone or download and extract the starter in that directory.

    git clone https://github.com/indaco/predix-hello-scala.git
    cd predix-hello-scala
    

    Running the app locally

    sbt
    
    > run-main WebServer
    

    Running in Predix Cloud

    1. Open the manifest.yml file and edit the name for your own application
    2. Push the app to your Predix account $cf push

    Copyright and License

    Licensed under the MIT License, see the LICENSE file.


    DISCLAIMER

    This is not an official development from the GE Digital’s Predix Team

    Visit original content creator repository
    https://github.com/indaco/predix-hello-scala

  • TFG-TFM-template

    Plantilla TFG/TFM de la ETSIN-UPM

    Plantilla en LaTeX para el Trabajo de Fin de Grado (TFG) o Trabajo de Fin de Máster (TFM) de la Escuela Técnica Superior de Ingenieros Navales de la Universidad Politécnica de Madrid (ETSIN-UPM). Contiene la estructura básica para la memoria del mismo, siguiendo la plantilla en Microsoft Word propuesta.

    Autor

    Este proyecto ha sido desarrollado por Ricardo López García (@ricardolopezgr).

    Licencia

    El código fuente se ha publicado bajo la licencia MIT. Los logos utilizados pertenecen a la Escuela Técnica Superior de Ingenieros Navales de la Universidad Politécnica de Madrid.

    Contribuir

    Si encuentras algún error o posible mejora no dudes en abrir una Issue o Pull Request.

    Estilo del texto

    En este capítulo se presenta el estilo general del texto que se desarrollará en formato de página A4. Se ha optado por un estilo Helvetica 11 pt (pudiendo optar por 12pt) a elección. Los márgenes recomendados son: superior 3 cm, inferior 1.5 cm, izquierdo 3 cm, derecho 1.75 cm.

    Esta plantilla de LaTeX comienza cada capítulo en página impar y deja, si es necesario, la página anterior vacía.

    Pueden desarrollarse los contenidos con distintos subapartados. Se trata en este documento de mostrar el formato elegido.

    El texto

    Se han de escribir las principales ideas, métodos, elementos de cálculo y de diseño utilizados. Recuerde que el número de páginas es limitado.

    Secciones y sub-secciones

    No conviene expandir más del nivel de sub-sección la estructura del texto.

    Los elementos gráficos

    Figuras

    Las figuras se numeran automáticamente con el número de capítulo seguida del número de figura en orden creciente. Su título está centrado y debajo de la figura.

    Se recomienda que las figuras vayan situadas adecuadamente en el texto. Recuerde que prioritariamente las figuras deben situarse en la parte alta de cada página. Sirva el siguiente ejemplo para ilustrar el formato de las figuras:

        \begin{figure}[H]
            \centering
            \includegraphics[width=0.8\textwidth]{images/figure_1.eps}
            \caption{La primera figura}
            \label{fig: isom}
        \end{figure}

    Recuerde insertar gráficas de alta calidad y a ser posible que se contraste bien lo que se quiere mostrar. No todos los documentos son impresos en color pese a las muy altas prestaciones gráficas de hoy en día.

    Para colocar varias gráficas, se recurre al entorno minipage.

    \begin{minipage}{0.5\textwidth}	
    	\begin{figure}[H] 
    		\includegraphics[width=1.00 \textwidth]{images/minipage1.eps}
    		\caption{La segunda figura}
    		\label{fig: minip}
    	\end{figure}	
    \end{minipage} \hfill \begin{minipage}{0.5\textwidth}	  
    	\begin{figure}[H] 
    		\includegraphics[width=1.00 \textwidth]{images/minipage2.eps}
    		\caption{La tercera figura}
    		\label{fig: minip2}
    	\end{figure}
    \end{minipage}

    Se recuerda que ambas gráficas deben estar muy relacionadas para mostrarse juntas.

    Tablas

    Las tablas se numeran también con el número del capítulo seguido del número de tabla en orden creciente. El título está centrado y en la parte superior de la tabla.

    Se recomienda que las tablas tengan información concisa y bien estructurada. Sirva el siguiente ejemplo para ilustrar el formato de las tablas:

     % Table generated by Excel2LaTeX from sheet 'Hoja1'
        \begin{table}[H]
        \centering
        \caption{Principales valores}
        \begin{tabular}{lrr}
            \toprule
            Variable   & Valor &   Unidad \\ \midrule
            Potencia   &   1.2 &       MW \\
            Velocidad  &   2.3 &      m/s \\
            Impedancia &   0.3 & $\Omega$ \\ \bottomrule
        \end{tabular}%
        \label{tab: valores}%
        \end{table}%

    Que produce un resultado similar a éste:

    Variable Valor Unidad
    Potencia 1.2 MW
    Velocidad 2.3 m/s
    Impedancia 0.3 Ω

    Una opción para realizar tablas es utilizar Excel y después generar el código mediante la macro Excel2LaTeX. Existen opciones similares para LibreOffice.

    Ecuaciones

    Para las ecuaciones, se pueden escribir en el modo “en línea” , produciendo el siguiente resultado (c^2=b^2+a^2) o bien numerándose para luego ser referenciadas, como se muestra a continuación.

        \begin{equation}
        ISE=\int_{0}^{\infty} \left(\widetilde{f}(\tau)-f(\tau)\right) d\tau
        \label{eq: ISE}
        \end{equation}

    Existen numerosos recursos en línea para editar las ecuaciones fácilmente. Se recomienda HostMath o Demo MathType.

    Algoritmos

    Para la exposición de un algoritmo u otro procedimiento que se requiera para la puesta en marcha, fabricación, proceso, etc. se puede recurrir al formato que se encuentra en el Anexo (ver GANXXX.pdf). Nótese que no se recomienda incluir código de programación o similares en el cuerpo del documento.

    Otros elementos

    Se incluyen aquí otros elementos sujetos a formato como pueden ser los siguientes.

    Listas enumeradas

    Se generan del siguiente modo:

    \begin{enumerate}
    	\item Primer elemento numerado.
    	\item Segundo elemento numerado.
    	\item ...
    	\item hasta el último
    \end{enumerate} 

    Que produce:

    1. Primer elemento numerado.

    2. Segundo elemento numerado.

    3. hasta el último

    Viñetas

    Se generan como:

    \begin{itemize}
    	\item Primer elemento numerado.
    	\item Segundo elemento numerado.
    	\item ...
    	\item hasta el último
    \end{itemize} 

    Dando como resultado:

    • Primer elemento.

    • Segundo elemento.

    • hasta el último

    Consejos

    Se aprovecha esta sección para dar algunos consejos respecto a la redacción de textos con LaTeX.

    • La distribución de LaTeX usada en este documento es MikTeX 2.9. Se recomienda usar esta versión frente a LiveTeX para evitar posibles errores al compilar.

    • El compilador es el que trae TeXStudio por defecto: pdfLaTeX.

    • Un editor muy usado y disponible en Windows, Mac y Linux es TeXstudio. Facilita ciertas operaciones como crear un environment, alineación de tablas, etc. A veces es necesario limpiar los archivos auxiliares que se generan para que el documento se compile más rápido. En TeXstudio, se hace en Tools > Limpiar archivos auxiliares.

    • Como alternativa se puede usar Overleaf, que permite realizar documentos en la web sin tener que instalar nada. Esta opción es muy interesante porque puedes trabajar desde cualquier lugar teniendo los archivos en línea creando una cuenta. No obstante, tiene sus limitaciones y para el documento final se recomienda una versión de escritorio.

    • Este documento ha sido dividido en capítulos, por lo que no será necesario compilar todos ellos cuando se esté trabajando en uno. Fácilmente se podrá incluir o no el capítulo usando el comando \include{CapituloX} en la raíz del documento. Los nombres de los archivos deben NO incluir espacios.

    • Se deberá hacer referencias a figuras, tablas, ecuaciones o incluso apartados durante el documento. Por ello, es recomendable usar el comando \label{eq: deformada} para asignar una etiqueta al objeto a referenciar, mientras que usaremos \ref{eq: deformada} para que se imprima la referencia. Los prefijos “eq:”, “fig:”, “tab” son muy útiles para no confundir referencias.

    • Se pueden incluir pies de página mediante el comando \footnote{Texto que se quiera mostar} para realizar aclaraciones.

    • Se recuerda que para poner alguna palabra entre comillas se usarán dos acentos graves al comienzo de la frase (``) y dos apóstrofos al final ('').

    • Para realizar una lista de términos y acrónimos (lo cual se recomienda), una manera alternativa a \makeglossary es incluir un capítulo sin numeración debajo de “Agradecimientos” que se llame “Términos y Acrónimos” y pegar una tabla sin bordes que se haya realizado y ordenado alfabéticamente en un Excel. Sería una tabla de dos columnas, con el acrónimo a la izquierda y su definición a la derecha.

    Información sobre la bibliografía

    Todos los documentos técnicos (Trabajo Fin de Grado, Tesis Doctoral, Artículo Técnico o Científico, Memoria, etc.) deben incluir una sección de bibliografía en la cual se hace un listado de todas las fuentes consultadas para realizar el trabajo. Es preciso otorgar el crédito a los trabajos realizados por otros y que se utilizan de algún modo u otro en el trabajo propio. Por esta razón, en el texto se deben incluir las referencias a las fuentes empleadas intentando incurrir en plagio, aún cuando ésta no sea nuestra intención. Se citará usando \cite{} .

    Todas las fuentes utilizadas deberían ser referenciadas en nuestro trabajo. Estas fuentes pueden ser:

    • Un libro o capítulo de libro

    • Un artículo de revista

    • Un artículo de congreso

    • Un manual técnico

    • Un trabajo anterior (Fin de Grado, Fin de Máster, Tesis Doctoral, etc.)

    • Un enlace virtual (Wikipedia, etc.)

    Se recomienda usar para la bibliografía programas como JabRef o BibTex para gestionar las referencias. El estilo más extendido en publicaciones es el IEEEtran, que en LaTeX se denomina ieeetr. Aparecen listados los trabajos a medida que se van citando, tal y como se puede comprobar en la siguiente página. Con este tipo de bibliografía, no aparecerán los trabajos hasta que éstos sean citados.

    El siguiente código genera la bibliografía (incluido en el archivo GANXXX.tex)

        \bibliographystyle{ieeetr}
        \addcontentsline{toc}{chapter}{\bibname}
        \bibliography{bibliographyfile}  
    Visit original content creator repository https://github.com/ricardolopezgr/TFG-TFM-template
  • Recursion-Question-practice

                        GNU GENERAL PUBLIC LICENSE
                           Version 3, 29 June 2007
    
     Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
     Everyone is permitted to copy and distribute verbatim copies
     of this license document, but changing it is not allowed.
    
                                Preamble
    
      The GNU General Public License is a free, copyleft license for
    software and other kinds of works.
    
      The licenses for most software and other practical works are designed
    to take away your freedom to share and change the works.  By contrast,
    the GNU General Public License is intended to guarantee your freedom to
    share and change all versions of a program--to make sure it remains free
    software for all its users.  We, the Free Software Foundation, use the
    GNU General Public License for most of our software; it applies also to
    any other work released this way by its authors.  You can apply it to
    your programs, too.
    
      When we speak of free software, we are referring to freedom, not
    price.  Our General Public Licenses are designed to make sure that you
    have the freedom to distribute copies of free software (and charge for
    them if you wish), that you receive source code or can get it if you
    want it, that you can change the software or use pieces of it in new
    free programs, and that you know you can do these things.
    
      To protect your rights, we need to prevent others from denying you
    these rights or asking you to surrender the rights.  Therefore, you have
    certain responsibilities if you distribute copies of the software, or if
    you modify it: responsibilities to respect the freedom of others.
    
      For example, if you distribute copies of such a program, whether
    gratis or for a fee, you must pass on to the recipients the same
    freedoms that you received.  You must make sure that they, too, receive
    or can get the source code.  And you must show them these terms so they
    know their rights.
    
      Developers that use the GNU GPL protect your rights with two steps:
    (1) assert copyright on the software, and (2) offer you this License
    giving you legal permission to copy, distribute and/or modify it.
    
      For the developers' and authors' protection, the GPL clearly explains
    that there is no warranty for this free software.  For both users' and
    authors' sake, the GPL requires that modified versions be marked as
    changed, so that their problems will not be attributed erroneously to
    authors of previous versions.
    
      Some devices are designed to deny users access to install or run
    modified versions of the software inside them, although the manufacturer
    can do so.  This is fundamentally incompatible with the aim of
    protecting users' freedom to change the software.  The systematic
    pattern of such abuse occurs in the area of products for individuals to
    use, which is precisely where it is most unacceptable.  Therefore, we
    have designed this version of the GPL to prohibit the practice for those
    products.  If such problems arise substantially in other domains, we
    stand ready to extend this provision to those domains in future versions
    of the GPL, as needed to protect the freedom of users.
    
      Finally, every program is threatened constantly by software patents.
    States should not allow patents to restrict development and use of
    software on general-purpose computers, but in those that do, we wish to
    avoid the special danger that patents applied to a free program could
    make it effectively proprietary.  To prevent this, the GPL assures that
    patents cannot be used to render the program non-free.
    
      The precise terms and conditions for copying, distribution and
    modification follow.
    
                           TERMS AND CONDITIONS
    
      0. Definitions.
    
      "This License" refers to version 3 of the GNU General Public License.
    
      "Copyright" also means copyright-like laws that apply to other kinds of
    works, such as semiconductor masks.
    
      "The Program" refers to any copyrightable work licensed under this
    License.  Each licensee is addressed as "you".  "Licensees" and
    "recipients" may be individuals or organizations.
    
      To "modify" a work means to copy from or adapt all or part of the work
    in a fashion requiring copyright permission, other than the making of an
    exact copy.  The resulting work is called a "modified version" of the
    earlier work or a work "based on" the earlier work.
    
      A "covered work" means either the unmodified Program or a work based
    on the Program.
    
      To "propagate" a work means to do anything with it that, without
    permission, would make you directly or secondarily liable for
    infringement under applicable copyright law, except executing it on a
    computer or modifying a private copy.  Propagation includes copying,
    distribution (with or without modification), making available to the
    public, and in some countries other activities as well.
    
      To "convey" a work means any kind of propagation that enables other
    parties to make or receive copies.  Mere interaction with a user through
    a computer network, with no transfer of a copy, is not conveying.
    
      An interactive user interface displays "Appropriate Legal Notices"
    to the extent that it includes a convenient and prominently visible
    feature that (1) displays an appropriate copyright notice, and (2)
    tells the user that there is no warranty for the work (except to the
    extent that warranties are provided), that licensees may convey the
    work under this License, and how to view a copy of this License.  If
    the interface presents a list of user commands or options, such as a
    menu, a prominent item in the list meets this criterion.
    
      1. Source Code.
    
      The "source code" for a work means the preferred form of the work
    for making modifications to it.  "Object code" means any non-source
    form of a work.
    
      A "Standard Interface" means an interface that either is an official
    standard defined by a recognized standards body, or, in the case of
    interfaces specified for a particular programming language, one that
    is widely used among developers working in that language.
    
      The "System Libraries" of an executable work include anything, other
    than the work as a whole, that (a) is included in the normal form of
    packaging a Major Component, but which is not part of that Major
    Component, and (b) serves only to enable use of the work with that
    Major Component, or to implement a Standard Interface for which an
    implementation is available to the public in source code form.  A
    "Major Component", in this context, means a major essential component
    (kernel, window system, and so on) of the specific operating system
    (if any) on which the executable work runs, or a compiler used to
    produce the work, or an object code interpreter used to run it.
    
      The "Corresponding Source" for a work in object code form means all
    the source code needed to generate, install, and (for an executable
    work) run the object code and to modify the work, including scripts to
    control those activities.  However, it does not include the work's
    System Libraries, or general-purpose tools or generally available free
    programs which are used unmodified in performing those activities but
    which are not part of the work.  For example, Corresponding Source
    includes interface definition files associated with source files for
    the work, and the source code for shared libraries and dynamically
    linked subprograms that the work is specifically designed to require,
    such as by intimate data communication or control flow between those
    subprograms and other parts of the work.
    
      The Corresponding Source need not include anything that users
    can regenerate automatically from other parts of the Corresponding
    Source.
    
      The Corresponding Source for a work in source code form is that
    same work.
    
      2. Basic Permissions.
    
      All rights granted under this License are granted for the term of
    copyright on the Program, and are irrevocable provided the stated
    conditions are met.  This License explicitly affirms your unlimited
    permission to run the unmodified Program.  The output from running a
    covered work is covered by this License only if the output, given its
    content, constitutes a covered work.  This License acknowledges your
    rights of fair use or other equivalent, as provided by copyright law.
    
      You may make, run and propagate covered works that you do not
    convey, without conditions so long as your license otherwise remains
    in force.  You may convey covered works to others for the sole purpose
    of having them make modifications exclusively for you, or provide you
    with facilities for running those works, provided that you comply with
    the terms of this License in conveying all material for which you do
    not control copyright.  Those thus making or running the covered works
    for you must do so exclusively on your behalf, under your direction
    and control, on terms that prohibit them from making any copies of
    your copyrighted material outside their relationship with you.
    
      Conveying under any other circumstances is permitted solely under
    the conditions stated below.  Sublicensing is not allowed; section 10
    makes it unnecessary.
    
      3. Protecting Users' Legal Rights From Anti-Circumvention Law.
    
      No covered work shall be deemed part of an effective technological
    measure under any applicable law fulfilling obligations under article
    11 of the WIPO copyright treaty adopted on 20 December 1996, or
    similar laws prohibiting or restricting circumvention of such
    measures.
    
      When you convey a covered work, you waive any legal power to forbid
    circumvention of technological measures to the extent such circumvention
    is effected by exercising rights under this License with respect to
    the covered work, and you disclaim any intention to limit operation or
    modification of the work as a means of enforcing, against the work's
    users, your or third parties' legal rights to forbid circumvention of
    technological measures.
    
      4. Conveying Verbatim Copies.
    
      You may convey verbatim copies of the Program's source code as you
    receive it, in any medium, provided that you conspicuously and
    appropriately publish on each copy an appropriate copyright notice;
    keep intact all notices stating that this License and any
    non-permissive terms added in accord with section 7 apply to the code;
    keep intact all notices of the absence of any warranty; and give all
    recipients a copy of this License along with the Program.
    
      You may charge any price or no price for each copy that you convey,
    and you may offer support or warranty protection for a fee.
    
      5. Conveying Modified Source Versions.
    
      You may convey a work based on the Program, or the modifications to
    produce it from the Program, in the form of source code under the
    terms of section 4, provided that you also meet all of these conditions:
    
        a) The work must carry prominent notices stating that you modified
        it, and giving a relevant date.
    
        b) The work must carry prominent notices stating that it is
        released under this License and any conditions added under section
        7.  This requirement modifies the requirement in section 4 to
        "keep intact all notices".
    
        c) You must license the entire work, as a whole, under this
        License to anyone who comes into possession of a copy.  This
        License will therefore apply, along with any applicable section 7
        additional terms, to the whole of the work, and all its parts,
        regardless of how they are packaged.  This License gives no
        permission to license the work in any other way, but it does not
        invalidate such permission if you have separately received it.
    
        d) If the work has interactive user interfaces, each must display
        Appropriate Legal Notices; however, if the Program has interactive
        interfaces that do not display Appropriate Legal Notices, your
        work need not make them do so.
    
      A compilation of a covered work with other separate and independent
    works, which are not by their nature extensions of the covered work,
    and which are not combined with it such as to form a larger program,
    in or on a volume of a storage or distribution medium, is called an
    "aggregate" if the compilation and its resulting copyright are not
    used to limit the access or legal rights of the compilation's users
    beyond what the individual works permit.  Inclusion of a covered work
    in an aggregate does not cause this License to apply to the other
    parts of the aggregate.
    
      6. Conveying Non-Source Forms.
    
      You may convey a covered work in object code form under the terms
    of sections 4 and 5, provided that you also convey the
    machine-readable Corresponding Source under the terms of this License,
    in one of these ways:
    
        a) Convey the object code in, or embodied in, a physical product
        (including a physical distribution medium), accompanied by the
        Corresponding Source fixed on a durable physical medium
        customarily used for software interchange.
    
        b) Convey the object code in, or embodied in, a physical product
        (including a physical distribution medium), accompanied by a
        written offer, valid for at least three years and valid for as
        long as you offer spare parts or customer support for that product
        model, to give anyone who possesses the object code either (1) a
        copy of the Corresponding Source for all the software in the
        product that is covered by this License, on a durable physical
        medium customarily used for software interchange, for a price no
        more than your reasonable cost of physically performing this
        conveying of source, or (2) access to copy the
        Corresponding Source from a network server at no charge.
    
        c) Convey individual copies of the object code with a copy of the
        written offer to provide the Corresponding Source.  This
        alternative is allowed only occasionally and noncommercially, and
        only if you received the object code with such an offer, in accord
        with subsection 6b.
    
        d) Convey the object code by offering access from a designated
        place (gratis or for a charge), and offer equivalent access to the
        Corresponding Source in the same way through the same place at no
        further charge.  You need not require recipients to copy the
        Corresponding Source along with the object code.  If the place to
        copy the object code is a network server, the Corresponding Source
        may be on a different server (operated by you or a third party)
        that supports equivalent copying facilities, provided you maintain
        clear directions next to the object code saying where to find the
        Corresponding Source.  Regardless of what server hosts the
        Corresponding Source, you remain obligated to ensure that it is
        available for as long as needed to satisfy these requirements.
    
        e) Convey the object code using peer-to-peer transmission, provided
        you inform other peers where the object code and Corresponding
        Source of the work are being offered to the general public at no
        charge under subsection 6d.
    
      A separable portion of the object code, whose source code is excluded
    from the Corresponding Source as a System Library, need not be
    included in conveying the object code work.
    
      A "User Product" is either (1) a "consumer product", which means any
    tangible personal property which is normally used for personal, family,
    or household purposes, or (2) anything designed or sold for incorporation
    into a dwelling.  In determining whether a product is a consumer product,
    doubtful cases shall be resolved in favor of coverage.  For a particular
    product received by a particular user, "normally used" refers to a
    typical or common use of that class of product, regardless of the status
    of the particular user or of the way in which the particular user
    actually uses, or expects or is expected to use, the product.  A product
    is a consumer product regardless of whether the product has substantial
    commercial, industrial or non-consumer uses, unless such uses represent
    the only significant mode of use of the product.
    
      "Installation Information" for a User Product means any methods,
    procedures, authorization keys, or other information required to install
    and execute modified versions of a covered work in that User Product from
    a modified version of its Corresponding Source.  The information must
    suffice to ensure that the continued functioning of the modified object
    code is in no case prevented or interfered with solely because
    modification has been made.
    
      If you convey an object code work under this section in, or with, or
    specifically for use in, a User Product, and the conveying occurs as
    part of a transaction in which the right of possession and use of the
    User Product is transferred to the recipient in perpetuity or for a
    fixed term (regardless of how the transaction is characterized), the
    Corresponding Source conveyed under this section must be accompanied
    by the Installation Information.  But this requirement does not apply
    if neither you nor any third party retains the ability to install
    modified object code on the User Product (for example, the work has
    been installed in ROM).
    
      The requirement to provide Installation Information does not include a
    requirement to continue to provide support service, warranty, or updates
    for a work that has been modified or installed by the recipient, or for
    the User Product in which it has been modified or installed.  Access to a
    network may be denied when the modification itself materially and
    adversely affects the operation of the network or violates the rules and
    protocols for communication across the network.
    
      Corresponding Source conveyed, and Installation Information provided,
    in accord with this section must be in a format that is publicly
    documented (and with an implementation available to the public in
    source code form), and must require no special password or key for
    unpacking, reading or copying.
    
      7. Additional Terms.
    
      "Additional permissions" are terms that supplement the terms of this
    License by making exceptions from one or more of its conditions.
    Additional permissions that are applicable to the entire Program shall
    be treated as though they were included in this License, to the extent
    that they are valid under applicable law.  If additional permissions
    apply only to part of the Program, that part may be used separately
    under those permissions, but the entire Program remains governed by
    this License without regard to the additional permissions.
    
      When you convey a copy of a covered work, you may at your option
    remove any additional permissions from that copy, or from any part of
    it.  (Additional permissions may be written to require their own
    removal in certain cases when you modify the work.)  You may place
    additional permissions on material, added by you to a covered work,
    for which you have or can give appropriate copyright permission.
    
      Notwithstanding any other provision of this License, for material you
    add to a covered work, you may (if authorized by the copyright holders of
    that material) supplement the terms of this License with terms:
    
        a) Disclaiming warranty or limiting liability differently from the
        terms of sections 15 and 16 of this License; or
    
        b) Requiring preservation of specified reasonable legal notices or
        author attributions in that material or in the Appropriate Legal
        Notices displayed by works containing it; or
    
        c) Prohibiting misrepresentation of the origin of that material, or
        requiring that modified versions of such material be marked in
        reasonable ways as different from the original version; or
    
        d) Limiting the use for publicity purposes of names of licensors or
        authors of the material; or
    
        e) Declining to grant rights under trademark law for use of some
        trade names, trademarks, or service marks; or
    
        f) Requiring indemnification of licensors and authors of that
        material by anyone who conveys the material (or modified versions of
        it) with contractual assumptions of liability to the recipient, for
        any liability that these contractual assumptions directly impose on
        those licensors and authors.
    
      All other non-permissive additional terms are considered "further
    restrictions" within the meaning of section 10.  If the Program as you
    received it, or any part of it, contains a notice stating that it is
    governed by this License along with a term that is a further
    restriction, you may remove that term.  If a license document contains
    a further restriction but permits relicensing or conveying under this
    License, you may add to a covered work material governed by the terms
    of that license document, provided that the further restriction does
    not survive such relicensing or conveying.
    
      If you add terms to a covered work in accord with this section, you
    must place, in the relevant source files, a statement of the
    additional terms that apply to those files, or a notice indicating
    where to find the applicable terms.
    
      Additional terms, permissive or non-permissive, may be stated in the
    form of a separately written license, or stated as exceptions;
    the above requirements apply either way.
    
      8. Termination.
    
      You may not propagate or modify a covered work except as expressly
    provided under this License.  Any attempt otherwise to propagate or
    modify it is void, and will automatically terminate your rights under
    this License (including any patent licenses granted under the third
    paragraph of section 11).
    
      However, if you cease all violation of this License, then your
    license from a particular copyright holder is reinstated (a)
    provisionally, unless and until the copyright holder explicitly and
    finally terminates your license, and (b) permanently, if the copyright
    holder fails to notify you of the violation by some reasonable means
    prior to 60 days after the cessation.
    
      Moreover, your license from a particular copyright holder is
    reinstated permanently if the copyright holder notifies you of the
    violation by some reasonable means, this is the first time you have
    received notice of violation of this License (for any work) from that
    copyright holder, and you cure the violation prior to 30 days after
    your receipt of the notice.
    
      Termination of your rights under this section does not terminate the
    licenses of parties who have received copies or rights from you under
    this License.  If your rights have been terminated and not permanently
    reinstated, you do not qualify to receive new licenses for the same
    material under section 10.
    
      9. Acceptance Not Required for Having Copies.
    
      You are not required to accept this License in order to receive or
    run a copy of the Program.  Ancillary propagation of a covered work
    occurring solely as a consequence of using peer-to-peer transmission
    to receive a copy likewise does not require acceptance.  However,
    nothing other than this License grants you permission to propagate or
    modify any covered work.  These actions infringe copyright if you do
    not accept this License.  Therefore, by modifying or propagating a
    covered work, you indicate your acceptance of this License to do so.
    
      10. Automatic Licensing of Downstream Recipients.
    
      Each time you convey a covered work, the recipient automatically
    receives a license from the original licensors, to run, modify and
    propagate that work, subject to this License.  You are not responsible
    for enforcing compliance by third parties with this License.
    
      An "entity transaction" is a transaction transferring control of an
    organization, or substantially all assets of one, or subdividing an
    organization, or merging organizations.  If propagation of a covered
    work results from an entity transaction, each party to that
    transaction who receives a copy of the work also receives whatever
    licenses to the work the party's predecessor in interest had or could
    give under the previous paragraph, plus a right to possession of the
    Corresponding Source of the work from the predecessor in interest, if
    the predecessor has it or can get it with reasonable efforts.
    
      You may not impose any further restrictions on the exercise of the
    rights granted or affirmed under this License.  For example, you may
    not impose a license fee, royalty, or other charge for exercise of
    rights granted under this License, and you may not initiate litigation
    (including a cross-claim or counterclaim in a lawsuit) alleging that
    any patent claim is infringed by making, using, selling, offering for
    sale, or importing the Program or any portion of it.
    
      11. Patents.
    
      A "contributor" is a copyright holder who authorizes use under this
    License of the Program or a work on which the Program is based.  The
    work thus licensed is called the contributor's "contributor version".
    
      A contributor's "essential patent claims" are all patent claims
    owned or controlled by the contributor, whether already acquired or
    hereafter acquired, that would be infringed by some manner, permitted
    by this License, of making, using, or selling its contributor version,
    but do not include claims that would be infringed only as a
    consequence of further modification of the contributor version.  For
    purposes of this definition, "control" includes the right to grant
    patent sublicenses in a manner consistent with the requirements of
    this License.
    
      Each contributor grants you a non-exclusive, worldwide, royalty-free
    patent license under the contributor's essential patent claims, to
    make, use, sell, offer for sale, import and otherwise run, modify and
    propagate the contents of its contributor version.
    
      In the following three paragraphs, a "patent license" is any express
    agreement or commitment, however denominated, not to enforce a patent
    (such as an express permission to practice a patent or covenant not to
    sue for patent infringement).  To "grant" such a patent license to a
    party means to make such an agreement or commitment not to enforce a
    patent against the party.
    
      If you convey a covered work, knowingly relying on a patent license,
    and the Corresponding Source of the work is not available for anyone
    to copy, free of charge and under the terms of this License, through a
    publicly available network server or other readily accessible means,
    then you must either (1) cause the Corresponding Source to be so
    available, or (2) arrange to deprive yourself of the benefit of the
    patent license for this particular work, or (3) arrange, in a manner
    consistent with the requirements of this License, to extend the patent
    license to downstream recipients.  "Knowingly relying" means you have
    actual knowledge that, but for the patent license, your conveying the
    covered work in a country, or your recipient's use of the covered work
    in a country, would infringe one or more identifiable patents in that
    country that you have reason to believe are valid.
    
      If, pursuant to or in connection with a single transaction or
    arrangement, you convey, or propagate by procuring conveyance of, a
    covered work, and grant a patent license to some of the parties
    receiving the covered work authorizing them to use, propagate, modify
    or convey a specific copy of the covered work, then the patent license
    you grant is automatically extended to all recipients of the covered
    work and works based on it.
    
      A patent license is "discriminatory" if it does not include within
    the scope of its coverage, prohibits the exercise of, or is
    conditioned on the non-exercise of one or more of the rights that are
    specifically granted under this License.  You may not convey a covered
    work if you are a party to an arrangement with a third party that is
    in the business of distributing software, under which you make payment
    to the third party based on the extent of your activity of conveying
    the work, and under which the third party grants, to any of the
    parties who would receive the covered work from you, a discriminatory
    patent license (a) in connection with copies of the covered work
    conveyed by you (or copies made from those copies), or (b) primarily
    for and in connection with specific products or compilations that
    contain the covered work, unless you entered into that arrangement,
    or that patent license was granted, prior to 28 March 2007.
    
      Nothing in this License shall be construed as excluding or limiting
    any implied license or other defenses to infringement that may
    otherwise be available to you under applicable patent law.
    
      12. No Surrender of Others' Freedom.
    
      If conditions are imposed on you (whether by court order, agreement or
    otherwise) that contradict the conditions of this License, they do not
    excuse you from the conditions of this License.  If you cannot convey a
    covered work so as to satisfy simultaneously your obligations under this
    License and any other pertinent obligations, then as a consequence you may
    not convey it at all.  For example, if you agree to terms that obligate you
    to collect a royalty for further conveying from those to whom you convey
    the Program, the only way you could satisfy both those terms and this
    License would be to refrain entirely from conveying the Program.
    
      13. Use with the GNU Affero General Public License.
    
      Notwithstanding any other provision of this License, you have
    permission to link or combine any covered work with a work licensed
    under version 3 of the GNU Affero General Public License into a single
    combined work, and to convey the resulting work.  The terms of this
    License will continue to apply to the part which is the covered work,
    but the special requirements of the GNU Affero General Public License,
    section 13, concerning interaction through a network will apply to the
    combination as such.
    
      14. Revised Versions of this License.
    
      The Free Software Foundation may publish revised and/or new versions of
    the GNU General Public License from time to time.  Such new versions will
    be similar in spirit to the present version, but may differ in detail to
    address new problems or concerns.
    
      Each version is given a distinguishing version number.  If the
    Program specifies that a certain numbered version of the GNU General
    Public License "or any later version" applies to it, you have the
    option of following the terms and conditions either of that numbered
    version or of any later version published by the Free Software
    Foundation.  If the Program does not specify a version number of the
    GNU General Public License, you may choose any version ever published
    by the Free Software Foundation.
    
      If the Program specifies that a proxy can decide which future
    versions of the GNU General Public License can be used, that proxy's
    public statement of acceptance of a version permanently authorizes you
    to choose that version for the Program.
    
      Later license versions may give you additional or different
    permissions.  However, no additional obligations are imposed on any
    author or copyright holder as a result of your choosing to follow a
    later version.
    
      15. Disclaimer of Warranty.
    
      THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
    APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
    HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
    OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
    THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
    PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
    IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
    ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
    
      16. Limitation of Liability.
    
      IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
    WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
    THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
    GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
    USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
    DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
    PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
    EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
    SUCH DAMAGES.
    
      17. Interpretation of Sections 15 and 16.
    
      If the disclaimer of warranty and limitation of liability provided
    above cannot be given local legal effect according to their terms,
    reviewing courts shall apply local law that most closely approximates
    an absolute waiver of all civil liability in connection with the
    Program, unless a warranty or assumption of liability accompanies a
    copy of the Program in return for a fee.
    
                         END OF TERMS AND CONDITIONS
    
                How to Apply These Terms to Your New Programs
    
      If you develop a new program, and you want it to be of the greatest
    possible use to the public, the best way to achieve this is to make it
    free software which everyone can redistribute and change under these terms.
    
      To do so, attach the following notices to the program.  It is safest
    to attach them to the start of each source file to most effectively
    state the exclusion of warranty; and each file should have at least
    the "copyright" line and a pointer to where the full notice is found.
    
        <one line to give the program's name and a brief idea of what it does.>
        Copyright (C) <year>  <name of author>
    
        This program is free software: you can redistribute it and/or modify
        it under the terms of the GNU General Public License as published by
        the Free Software Foundation, either version 3 of the License, or
        (at your option) any later version.
    
        This program is distributed in the hope that it will be useful,
        but WITHOUT ANY WARRANTY; without even the implied warranty of
        MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
        GNU General Public License for more details.
    
        You should have received a copy of the GNU General Public License
        along with this program.  If not, see <https://www.gnu.org/licenses/>.
    
    Also add information on how to contact you by electronic and paper mail.
    
      If the program does terminal interaction, make it output a short
    notice like this when it starts in an interactive mode:
    
        <program>  Copyright (C) <year>  <name of author>
        This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
        This is free software, and you are welcome to redistribute it
        under certain conditions; type `show c' for details.
    
    The hypothetical commands `show w' and `show c' should show the appropriate
    parts of the General Public License.  Of course, your program's commands
    might be different; for a GUI interface, you would use an "about box".
    
      You should also get your employer (if you work as a programmer) or school,
    if any, to sign a "copyright disclaimer" for the program, if necessary.
    For more information on this, and how to apply and follow the GNU GPL, see
    <https://www.gnu.org/licenses/>.
    
      The GNU General Public License does not permit incorporating your program
    into proprietary programs.  If your program is a subroutine library, you
    may consider it more useful to permit linking proprietary applications with
    the library.  If this is what you want to do, use the GNU Lesser General
    Public License instead of this License.  But first, please read
    <https://www.gnu.org/licenses/why-not-lgpl.html>.
    

    Visit original content creator repository
    https://github.com/yashvardhan-rustedlegend/Recursion-Question-practice

  • GlusterFS

    gluster-ant

    What is GlusterFS ?

    • Gluster is a free and open source software scalable network filesystem.
    • it use Disk –> Brick –> Volume to serve client data
    • we can config it in two ways :
      1- Replicated HA
      2- Distributed Scale
    • in Replication HA Method , if you Write 1G Data to DB , Based on your Replicaset , for example 3 , You have 3 instabce from your data and of course your data occupied 3G on your servers . now if one of your server goes down , you can retrive your data from other nodes .
    • now if you have one big file , for example 150 GB , and your disks on linux server have just 100 GB per nodes , you can not write yor data file into your replicated cluster and you should use DISTRIBUTED mode . in this mode , for example if you have 3 server with 100 GB stroage for glusterfs , now you have totally 300GB for storing data . but in Replicated Method you just have 100GB Storage . BUT if one of your server goes down in distributed method , you have lost you data .
    • we can use two protocol to communicate between client and cluster . one of them is nfs and another is Gluster Protocol . gluster
    Visit original content creator repository https://github.com/amirajoodani/GlusterFS
  • StereoTool

    JP Stereo Tool

    A stereo balance and phase correlation meter for Bitwig Studio, with optional handy controls for shaping the stereo image.

    User Interface Overview

    The default Metering View provides a streamlined monitoring interface:

    1. Balance Meter: Indicates the perceived center position (balance) within the stereo field.
    2. Correlation Meter: Displays how well the left and right channels are aligned (phase correlation).
    3. Knob List: Toggles between the Metering View and the Control View.

    The Control View offers access to stereo shaping controls:

    1. Stereoize Knob: Adds extra stereo content to a mono or stereo signal (stereo enhancement).
    2. Width Knob: Adjusts the width of a stereo signal (side loudness).
    3. Panning Knob: Shifts the signal’s position within the stereo field (true stereo panning).
    4. Meters Knob: Adjusts the responsiveness of the meters’ movement (average measurement time).

    How to Install

    The GitHub repository for JP Stereo Tool contains all releases, as well as documentation and license information.

    1. Download the “JP-Stereo-Tool-Download.zip” file from the repository’s Latest Release page.
    2. Unzip the downloaded file to access the “JP Stereo Tool.bwpreset” file.
    3. Drag and drop the “JP Stereo Tool.bwpreset” file onto a track in Bitwig Studio’s arrangement or mixer window.
    4. In Bitwig Studio, right-click on the device you just added and select “Save Preset to Library” to make it easily accessible later.

    Alternatively, you can copy the downloaded “JP Stereo Tool.bwpreset” file directly into Bitwig Studio’s library “Presets” folder, which can be found at:

    • Linux and macOS: “~/Documents/Bitwig Studio/Library/Presets”
    • Windows: “%userprofile%\Documents\Bitwig Studio\Library\Presets”

    Note

    Before installing, ensure you have the full version of Bitwig Studio. It is recommended to use the latest version. This device was specifically tested with Bitwig Studio version 5.2.7.

    Usage Guide

    Balance Meter

    The Balance Meter indicates the perceived center position (balance) within the stereo field. The indicator moves dynamically from left to right, showing whether the left or right channel is more dominant.

    Tip

    For a well-balanced stereo mix, the indicator should typically hover near the center, reflecting an even distribution between the left and right channels.

    Correlation Meter

    The Correlation Meter displays how well the left and right channels are aligned (phase correlation). The indicator moves dynamically from left (channels are fully out of phase) to right (channels are perfectly in phase).

    Tip

    For better mono compatibility, aim for the indicator to stay mostly between the center and the right side of the meter.

    Stereoize Knob

    The Stereoize Knob adds extra stereo content to a mono or stereo signal (stereo enhancement), with settings ranging from 0% (no effect, default) to 100% (maximum enhancement). Since the Stereoize Knob is mono-compatible, it will not produce any audible effect if the Width Knob is set to -100% (mono).

    Tip

    Fine-tune the Stereoize Knob amount while aiming for a natural-sounding result, then adjust the Width Knob amount for desired width. For widening a mono sound, a setting worth trying is Stereoize at +67% and Width at +57%.

    Width Knob

    The Width Knob adjusts the width of a stereo signal (side loudness), ranging from -100% (fully mono) to +100% (double the original width), with a default setting of 0% (unaltered). To widen a mono signal, which lacks side information by definition, use the dedicated Stereoize Knob.

    Tip

    To improve coherency in the stereo image, try reducing the width of wider sounds and panning them to distinct positions in the stereo field.

    Panning Knob

    The Panning Knob shifts the signal’s position within the stereo field (true stereo panning), ranging from -100% (hard left) to +100% (hard right), with a default value of 0% (unaltered).

    Tip

    After setting the desired stereo position, experiment with the Width Knob amount to improve the overall balance of your mix.

    Meters Knob

    The Meters Knob adjusts the responsiveness of the meters’ movement (average measurement time), ranging from -100% (very slow) to +100% (very fast), with a default value of 0% (balanced).

    Tip

    It is best to stick with a consistent Meters Knob setting to build familiarity with the meters’ readouts. The default setting is a good starting point.

    Geeky Insights

    Ever wondered what is really going on behind the scenes? This section dives deeper for curious minds.

    JP Stereo Tool is a native Bitwig Studio device, using a bit of audio routing trickery to sidestep signal alterations introduced by the FX Grid. The meters come alive through a creative (mis)use of the Steps modulators.

    The device adds 34 samples (about 0.7 ms) of compensated latency. CPU usage is generally low, but gets a bit more of a workout when the Stereoize Knob is set to a non-zero value.

    The signal chain follows the order: Stereoize > Width > Panning > Meters. This arrangement allows each control to progressively shape the stereo image, with the order of the user interface knobs reflecting the internal signal chain.

    If the Stereoize, Width, or Panning knob is nudged away from its default position, the device starts altering the audio signal. When those knobs are set to their default positions, the audio signal remains untouched, which is crucial for monitoring-only purposes.

    The Balance Meter calculates the difference between the RMS values of the left and right channels, normalized by their sum. The Correlation Meter computes the mean product of the left and right channels, normalized by the square root of the product of their RMS values. The Meters Knob controls the averaging window time used in these calculations.

    The Stereoize Knob splits the signal into three bands using 18 dB-per-octave crossover filters and applies complementary comb filtering to the left and right channels in the middle band. As the amount is raised, the mix between the original and the artificially enhanced signal increases, while the frequency of complementary notches and peaks shifts gradually, making it easier to dial in the sweet spot.

    The Width Knob is mapped directly to Bitwig Studio’s Tool device’s Width control. It works simply by altering the volume of the side signal.

    The Panning Knob uses true stereo panning, allowing the image to shift without altering the left-right gain relationship. In contrast, typical balance-based panning simply lowers the level of one channel, which can cause parts of a stereo signal to vanish. For example, hard-panning a sound with a ping-pong delay using balance-based panning would make one side inaudible (either the “ping” or the “pong”).

    Tip

    When in doubt, listen to your stereo mix in mono. Believe the meters, but trust your ears, always. May the balance be with you!

    License

    You are free to use, modify, and distribute this device in any way you choose. While no attribution is required, feel free to link back to the GitHub repository if you would like to credit the project.

    For legal details, refer to the full terms provided in the LICENSE file included in the repository.

    Note

    This is a hobby project shared as-is. I will truly appreciate your effort in providing feedback via Discussions and submitting Issues, but please be aware that my direct replies may be limited.

    Visit original content creator repository https://github.com/JanuszPelc/StereoTool