Electrode potential | Go To Index | Electromigration | ||||||||||||||||||||||||||||||
Electrolytic polishing
A method that is used in particular for the preparation of microscopy samples. For example, a sample of pure tin, a sample of single-phase alloy or a binary Sn-Pb alloy is used as the anode, placed in an appropriate etching solution and then current is generated between the anode and a suitable cathode. Depending on the voltage and current density, metal is separated from the surface from time to time, creating a surface that is ready for microscopy. The etching is, however, most intense at the edges of the sample. This method is applicable to certain alloys only because in samples with two or more phases, it is difficult to process all with the same removal rate which may lead to an incomplete polishing. If the structure consists of one or more phases, a completely uniform removal of the surface is impossible even when applying special electrolytes or specific conditions and samples may become too unpolished or too strongly etched. Even if two different phases contact each other in the electrolyte solution, a galvanic reaction occurs between them with difficulty and this reduces the chances of achieving a quality finish that would match mechanical polishing. Mechanically polished samples as well as samples polished electrically with success are then electrically etched. The sample is placed into the prepared etching solution and processed with a stronger current than during polishing. If only a certain phase of the alloy is of interest, electro-polishing is easier to monitor and quantitatively adjust than chemical etching. The former has the advantage of being able to separate crystal grains, grain boundaries, single phases, more layers or certain metallic components from the surrounding matrix. Furthermore, as opposed to mechanical polishing, it leaves no cracks on the polished surface. If large amounts of similar samples need regular examination, electropolishing is overall more effective than manual polishing and etching. Suitable polishing fluids and conditions for Sn alloys are listed in the following table. Three of the electrolyte fluids are chlorine-based and highly explosive at high temperature; extra caution is advised. Since two samples are seldom identical, electrolysis conditions must be adapted in each case. Electropolishing solutions for tin-based alloys
Electropolishing solutions for tin-based alloys
|
Name | Domain | Description | Category |
---|---|---|---|
stripemid | Wird von Font Awesome verwendet, um den Zahlungszugriff auf den Drittanbieter-Service zu verfolgen. | Functional | |
utma | Dieses Cookie zählt, wie oft ein Besucher auf der Website war, als der erste und der letzte Besuch stattfanden. | Functional | |
utmz | Registriert den Standort und die Passwörter des Benutzers. | Functional | |
fbp | Wird von Facebook verwendet, um eine Reihe von Werbeprodukten anzuzeigen, beispielsweise Echtzeitgebote von Werbekunden Dritter. | Functional | |
utmc | Überprüft, ob die Sitzung geöffnet bleiben muss oder eine neue Sitzung geöffnet werden muss. | Functional |
Name | Domain | Description | Category |
---|---|---|---|
Functional |
Name | Domain | Description | Category |
---|---|---|---|
cookiePreferences | Advertiser's website domain (1st party) | Registers cookie preferences of a user | Functional |
Name | Domain | Description | Category |
---|---|---|---|
_GRECAPTCHA | google.com | Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis. | Functional |
Name | Domain | Description | Category |
---|---|---|---|
testcookie | doubleclick.net | Testen die Browser-Einstellungsberechtigungen im Browser des Benutzers | Marketing |
IDE | doubleclick.net | Marketing |
Name | Domain | Description | Category |
---|---|---|---|
_ga | google-analytics.com (3rd party) or advertiser's website domain (1st party) | ID used to identify users | Analytics |
_ga_ | google-analytics.com (3rd party) or advertiser's website domain (1st party) | ID used to identify users | Analytics |
_gid | google-analytics.com (3rd party) or advertiser's website domain (1st party) | ID used to identify users for 24 hours after last activity | Analytics |
_gat | google-analytics.com (3rd party) or advertiser's website domain (1st party) | Used to monitor number of Google Analytics server requests when using Google Tag Manager | Analytics |
_dc_gtm_ | google-analytics.com (3rd party) or advertiser's website domain (1st party) | Used to monitor number of Google Analytics server requests | Analytics |
AMP_TOKEN | google-analytics.com (3rd party) or advertiser's website domain (1st party) | Contains a token code that is used to read out a Client ID from the AMP Client ID Service. By matching this ID with that of Google Analytics, users can be matched when switching between AMP content and non-AMP content. Reference: https://support.google.com/analytics/answer/7486764?hl=en | Analytics |
_gat_gtag_ | google-analytics.com (3rd party) or advertiser's website domain | Used to set and get tracking data | Analytics |
_gac_ | google-analytics.com (3rd party) or advertiser's website domain (1st party) | Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together. | Marketing |
__utma | google-analytics.com (3rd party) or advertiser's website domain (1st party) | ID used to identify users and sessions | Analytics |
__utmt | google-analytics.com (3rd party) or advertiser's website domain (1st party) | Used to monitor number of Google Analytics server requests | Analytics |
__utmb | google-analytics.com (3rd party) or advertiser's website domain (1st party) | Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server. | Analytics |
__utmc | google-analytics.com (3rd party) or advertiser's website domain (1st party) | Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session. | Analytics |
__utmz | google-analytics.com (3rd party) or advertiser's website domain (1st party) | Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server | Analytics |
__utmv | google-analytics.com (3rd party) or advertiser's website domain (1st party) | Bevat custom informatie die door de webdeveloper is ingesteld via de _setCustomVar methode in Google Analytics. Deze cookie wordt iedere keer geupdate als er nieuwe gegevens naar de Google Analytics server worden gestuurd. | Analytics |
__utmx | google-analytics.com (3rd party) or advertiser's website domain (1st party) | Used to determine whether a user is included in an A / B or Multivariate test. | Analytics |
__utmxx | google-analytics.com (3rd party) or advertiser's website domain (1st party) | Used to determine when the A / B or Multivariate test in which the user participates ends | Analytics |
Name | Domain | Description | Category |
---|---|---|---|
GPS | youtube.com (3rd party) | Registers a unique ID on mobile devices to enable tracking based on geographical GPS location. | Marketing |
VISITOR_INFO1_LIVE | youtube.com (3rd party) | Tries to estimate the users' bandwidth on pages with integrated YouTube videos. | Marketing |
PREF | youtube.com (3rd party) | This cookie stores your preferences and other information, in particular preferred language, how many search results you wish to be shown on your page, and whether or not you wish to have Google’s SafeSearch filter turned on. | Functional |
YSC | youtube.com (3rd party) | Registers a unique ID to keep statistics of what videos from YouTube the user has seen. | Functional |