Archivo

Contexto: Una fábrica produce piezas mecánicas que deben pasar por un proceso de inspección de calidad. Si una pieza no cumple con los estándares de calidad, se envía a retrabajo.

El proceso de retracodigo2ene una probabilidad de éxito, después de lo cual la pieza se vuelve a inspeccionar. Si la pieza falla nuevamente, se descarta.

1. Tasa de producción: 10 piezas por hora.

2. Tiempo de inspección: 5 minutos por pieza.

3. Probabilidad de falla en la inspección inicial: 20%.

4. Tiempo de retrabajo: 15 minutos por pieza.

5. Probabilidad de éxito en el retrabajo: 70%.

6. Tiempo de inspección después del retrabajo: 5 minutos por pieza. 7.

Cantidad máxima de retrabajo: 3

Objetivo: Simular el proceso durante un turno de 8 horas para determinar:

1. El número total de piezas producidas.
2. El número de piezas que pasan la inspección inicial.
3. El número de piezas que requieren retrabajo.
4. El número de piezas que pasan la inspección después del retrabajo.
5. El número de piezas descartadas.
6. El tiempo total de espera en cola para retrabajo.

1. Generar las piezas: Crear un evento de llegada de piezas cada 6 minutos (10 piezas por hora).
2. Inspección inicial: Para cada pieza, determinar si pasa o falla la inspección inicial (20% de probabilidad de falla).
3. Retrabajo: Para las piezas que fallan, enviar a retrabajo si hay capacidad disponible; si no, esperar en cola.
4. Resultados: Registrar los resultados de cada inspección y retrabajo, así como el tiempo de espera en cola.

Writing in Markua is easy! You can learn most of what you need to know with just a few examples.

To make italic text you surround it with single asterisks. To make bold text you surround it with double asterisks.

You can start new sections by starting a line with two # signs and a space, and then typing your section title.

You can start new sub-sections by starting a line with three # signs and a space, and then typing your sub-section title.

At the top of this file, you will also see a line at the top:

Leanpub has the ability to make a sample book, which interested readers can download or read online. If you add this line above a chapter heading, then when you publish your book, this chapter will be included in a separate sample book for these interested readers.

You can add web links easily.

Here’s a link to the Leanpub homepage.

You can add an image to your book in a similar way.

First, add the image to the “Resources” folder for your book. You will find the “Resources” folder under the “Manuscript” menu to the left.

If you look in your book’s “Resources” folder right now, you will see that there is an example image there with the file name “palm-trees.jpg”. Here’s how you can add this image to your book:

If you want to add a figure title, you put it in quotes:

If you want to add descriptive alt text, which is good for accessibility, you put it between the square brackets:

You can also set the alt text and/or the figure title in an attribute list:

Finally, if no title is provided, and the alt-title document setting is the default of all, the alt text will be used as the figure title instead of as alt text.

You can set the important document settings at Settings > Generation Settings.

You make a numbered list like this:

1. kale
2. carrot
3. ginger

You make a bulleted list like this:

• kale
• carrot
• ginger

You can even have definition lists!

term 1

definition 1a

definition 1b

term 2

definition 2

You can add code samples really easily. Code can be in separate files (a “local” resource) or in the manuscript itself (an “inline” resource).

Here’s a local code resource:

como se escribe

Inline code samples can either be spans or figures.

A span looks like puts "hello world" this.

A figure looks like this:

You can also add a figure title using the title attribute:

You can insert tables easily inline, using the GitHub Flavored Markdown (GFM) table syntax:

Tables work best for numeric tabular data involving a small number of columns containing small numbers:

Definition lists are preferred to tables for most use cases, since reading a large table with many columns is terrible on phones and since typing text in a table quickly gets annoying.

You can easily insert math equations inline using either spans or figures.

Here’s one of the kinematic equations inserted as a span inside a sentence.

Here’s some math inserted as a figure.

Markua supports both of Markdown’s heading styles.

The preferred style, called atx headers, has the following meaning in Markua:

Note the use of three backticks in the above example, to treat the Markua like inline code (instead of actually like headers).

The other style of headers, called Setext headers, has the following headings:

Setext headers look nice, but only if you’re only using chapters and sections. If you want to add sub-sections (or lower), you’ll be using atx headers for at least some of your headers. My advice is to just use atx headers all the time. (The {class: part} attribute list on a chapter header to make a part header does actually work with Setext headers, but it’s really ugly.)

Note that while it is confusing and ugly to mix and match using atx and Setext headers for chapters and sections in the same document, you can do it. However, please don’t.

Block quotes are really easy too.

—Peter Armstrong, Markua Spec

There are many types of blurbs, which will be familiar to you if you’ve ever read a computer programming book.

You can also specify them this way:

If you’ve read this far, you’re definitely the right type of person to be here!

Our last piece of advice is simple: once you have a couple chapters completed, publish your book in-progress!

This approach is called Lean Publishing. It’s why Leanpub is called Leanpub.

If you want to learn more about Lean Publishing, read this or watch this.

comentario