This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
your_first_page [2018/03/14 01:28] mcmaster [Chip pages] |
your_first_page [2024/01/15 08:47] (current) mcmaster |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| TLDR: | TLDR: | ||
| - | * Copy another page as an example | + | * Most users should use [[tool: |
| + | * You may need to request access | ||
| + | * Alternatively: | ||
| * Upload pages and images to your assigned namespace | * Upload pages and images to your assigned namespace | ||
| * Admins will help setup your landing page and possibly your first page | * Admins will help setup your landing page and possibly your first page | ||
| - | * Image files talks about sample workflow | + | * "Image files" section goes through |
| Line 16: | Line 18: | ||
| * Some devices may be considered sensitive for various reasons, or you may simply not wish to let the public know that you're studying a certain chip until you've finished your analysis. Pages may be placed in the " | * Some devices may be considered sensitive for various reasons, or you may simply not wish to let the public know that you're studying a certain chip until you've finished your analysis. Pages may be placed in the " | ||
| * We have some [[: | * We have some [[: | ||
| + | |||
| + | |||
| + | ====== Chip pages ====== | ||
| + | |||
| + | Generally just [[mcmaster: | ||
| + | |||
| + | For example, to create a page for collection " | ||
| + | |||
| + | High resolution chip maps must be added manually by mcmaster. Generally, low resolution images (say below 5 MB) should just be added to the pages directly and not map'd. See below for suggested workflow for low resolution images. | ||
| + | |||
| + | mcmaster uses [[https:// | ||
| + | |||
| + | ====== Image files ====== | ||
| + | |||
| + | TLDR: | ||
| + | * Small image (< 5 MB): add to wiki pages | ||
| + | * You must place these in your namespace, ideally in a page specific namespace (see below for details) | ||
| + | * Don't worry too much about file name, but you can use high large imaging naming as guidance if you want | ||
| + | * Import [[tool: | ||
| + | * Large images: they should be added with simapper | ||
| + | * See tool page [[tool: | ||
| + | * You may need to request access from an admin (ie McMaster) | ||
| + | * See [[: | ||
| + | |||
| + | Suggested low resolution image workflow: | ||
| + | * Put image in a namespace named after the page | ||
| + | * Ex: for mcmaster: | ||
| + | * Edit page mcmaster: | ||
| + | * This can be done by copying and pasting the url, including setting up the edit | ||
| + | * Ex: https:// | ||
| + | * Hit " | ||
| + | * Upload the image, placing it into the mcmaster: | ||
| + | * Click on it to get markdown for the image | ||
| + | * Cut and paste that into the original page (mcmaster: | ||
| + | |||
| + | Please upload photos in JPEG format at quality 90 and use PNG for diagrams. When possible, all images should be captured in a lossless form such as TIFF and converted to JPEG for web purposes. Lossless compression reduces artifacts and makes the images more friendly for machine vision, so the original files should be used for analysis when possible. | ||
| + | |||
| + | Images above say 5 MB (say 16 megapixels) should be downsampled before posting in order to prevent the thumbnailer from running out of memory. High-resolution stitches are welcome but we currently do not have an automated interface for uploading map images, please contact an admin if you have one to contribute. | ||
| + | |||
| ====== User pages ====== | ====== User pages ====== | ||
| Line 32: | Line 73: | ||
| You can, of course, add extra information about yourself if you'd like. Typically this would be a summary of your interests/ | You can, of course, add extra information about yourself if you'd like. Typically this would be a summary of your interests/ | ||
| + | |||
| ====== Vendor pages ====== | ====== Vendor pages ====== | ||
| Line 47: | Line 89: | ||
| Additional information which might be useful here is a description of what kind of products the company makes, dates of major events (founded, went out of business, bought/was bought by another company). | Additional information which might be useful here is a description of what kind of products the company makes, dates of major events (founded, went out of business, bought/was bought by another company). | ||
| - | ====== Chip pages ====== | ||
| - | |||
| - | High resolution chip maps must be added manually by mcmaster. Generally, low resolution images (say below 5 MB) should just be added to the pages directly and not map'd. | ||
| - | |||
| - | Generally just copy another page or [[template|us this template]] | ||
| - | |||
| - | TOOD: add more detail | ||
| - | |||
| - | TODO: mcmaster uses a script to template most pr0nmap pages. Add a link to it | ||
| - | |||
| - | |||
| - | ====== Image files ====== | ||
| - | |||
| - | TLDR: | ||
| - | * Upload small images (< 5 MB) to wiki pages | ||
| - | * Submit large images to McMaster to mapify | ||
| - | * See [[: | ||
| - | |||
| - | Suggested low resolution image workflow: | ||
| - | * Put image in a namespace named after the page | ||
| - | * Ex: for mcmaster: | ||
| - | * Edit page mcmaster: | ||
| - | * This can be done by copying and pasting the url, including setting up the edit | ||
| - | * Ex: https:// | ||
| - | * Hit " | ||
| - | * Upload the image, placing it into the mcmaster: | ||
| - | * Click on it to get markdown for the image | ||
| - | * Cut and paste that into the original page (mcmaster: | ||
| - | |||
| - | Please upload photos in JPEG format at quality 90 and use PNG for diagrams. When possible, all images should be captured in a lossless form such as TIFF and converted to JPEG for web purposes. Lossless compression reduces artifacts and makes the images more friendly for machine vision, so the original files should be used for analysis when possible. | ||
| - | |||
| - | Images above say 5 MB (say 16 megapixels) should be downsampled before posting in order to prevent the thumbnailer from running out of memory. High-resolution stitches are welcome but we currently do not have an automated interface for uploading map images, please contact an admin if you have one to contribute. | ||
| - | |||
| - | ===== Non-microscope images ===== | ||
| - | |||
| - | TODO: Come up with naming convention | ||
| - | |||
| - | ===== SEM images ===== | ||
| - | |||
| - | azonenberg' | ||
| - | |||
| - | " | ||
| - | Magnification should be abbreviated if a multiple of 1000, otherwise written out in full (ex: 3900x, 4kx). | + | ====== Quick add / mass import ====== |
| - | Working distance and accelerating voltage should also be specified to aid in interpretation | + | In May 2021 a number |
| - | ===== Optical microscope images ===== | + | simapper |
| + | * Upload a conforming file name to the form | ||
| + | * Template page is created and map is created | ||
| + | * It's currently possible to mass import using a table, but this is fragile and might get removed | ||
| - | Images should be named " | + | sipager (file) |
| + | * Upload a conforming file name to the form | ||
| + | * Template page is created with the image added as a single die photo | ||
| - | If you've calibrated your microscope against a standard of some sort, please add an overlay with the objective name and a scale bar to your images. | + | sipager |
| + | * Currently | ||
| + | * Template page is created | ||
| + | * All images in directory are added to page | ||
| + | * Additional information from optional | ||
| + | * Consider .tar version to allow uploading to form | ||