1. Very long, but very intresting and important content
2. Very long, but very intresting and important content
3. Very long, but very intresting and important content
4. Very long, but very intresting and important content
5. Very long, but very intresting and important content
6. Very long, but very intresting and important content
7. Very long, but very intresting and important content
8. Very long, but very intresting and important content
9. Very long, but very intresting and important content
10. Very long, but very intresting and important content
11. Very long, but very intresting and important content
12. Very long, but very intresting and important content
13. Very long, but very intresting and important content


Docker is a platform that gives users the capability to to package and run applications inside an isolated environment
reffered to as a 'container.' Docker's website provides useful information on docker uses and applications such as the following:
Docker runs off the central CPU kernel and therfore utilizes less resources than virtual machines
Docker allows you to develop your application and its supporting components using containers.
The container becomes the unit for distributing and testing your application.
When you’re ready, deploy your application into your production environment, as a container or an orchestrated service. This works the same whether your production environment is a local data center, a cloud provider, or a hybrid of the two.


This sample demonstrates
the basics of writing a GFX property page. It can be used as a starting point
for writing your own GFX property dialog. The sample works only in conjunction
with the audio GFX filter sample, which is tied to the Microsoft DSS 80 USB
speakers. To adapt the sample to work with a different set of USB speakers,
modify the INF file by replacing the Plug and Play device ID of the Microsoft
DSS 80 USB speakers with the device ID of your USB speakers.
After you have installed
both the audio GFX filter and this sample, the property dialog will appear when
you open the Advanced Audio Properties dialog and click on the Properties
button for the USB speakers in the Effects tab. Through this dialog, you
can enable or disable channel-swapping by the GFX filter.
NOTE: This sample will only build for
32-bit Microsoft® Windows® XP and later platforms.
To build this sample,
enter the free or checked Windows XP build environment and run
the build command from the main GFX sample directory (parent directory),
rather than from this subdirectory. This command also builds the audio GFX
filter sample, which this sample requires to work properly.
After you have built the
sample, use the INF file gfxswap.inf, which is
included in the parent directory, to install the sample. Simply copy the INF
file, the binary file for this sample, and the GFX filter binary to a floppy
disk. Next, to install the samples, display the floppy contents in Windows
Explorer, right-click the INF file, and choose to Install
on your test machine. For more information, see the readme.htm file in the
parent directory.
After the INF file has
installed the driver, you can update and test your new versions of the sample by copying the binary into the %SystemRoot%\system32
directory on the target machine and rebooting. This technique is sufficient
unless you also make changes to the INF file.
This sample works only
with the Windows XP (or later) operating system.
The GFX
property dialog sample communicates with the GFX filter by sending property
requests. The sample sends a property request to the GFX filter's single node.
Because the node type is new (specific to the GFX filter sample), the property
is new (private) as well.
The project was generated using the ATL Wizard in Microsoft Visual C++® 6.0. The project workspace file is included in the sample files so that you can open the project with Microsoft Visual C++ 6.0 (or later). If you want to create your own project, the preferred method is to use the wizard to create a new project instead of renaming this project and modifying it. If you choose to do the latter anyway, be sure to read the discussion of GUID dependencies in the readme.htm file in the parent directory.
|
|
© 2004 Microsoft
Corporation


Physical memory definitions for processors without MMU. More...
#include <stdint.h>
Go to the source code of this file.
Defines | |
| #define | PHYS_MAP_COHERENT (0) |
| Create a coherent (uncached) mapping. | |
| #define | PHYS_MAP_WRBUF (0) |
| Write-buffering is allowed. | |
| #define | PHYS_MAP_WRTHROUGH (0) |
| Write-through caching is allowed. | |
| #define | PHYS_MAP_WRBACK (0) |
| Write-back caching is allowed. | |
Functions | |
| static void * | physmem_map (phys_addr_t phys, phys_size_t size, unsigned long flags) |
| Map a physical address to a virtual address. | |
| static void | physmem_unmap (void *vaddr, phys_size_t size) |
| Unmap a virtual-to-physical mapping. |
Physical memory definitions for processors without MMU.
This file is intended to be included from cpu/physmem.h on processors without a Memory Management Unit (MMU). Do not include this file directly!
Copyright (C) 2009 Atmel Corporation. All rights reserved.
Definition in file physmem_nommu.h.
| #define PHYS_MAP_COHERENT (0) |
Create a coherent (uncached) mapping.
Definition at line 50 of file physmem_nommu.h.
| #define PHYS_MAP_WRBACK (0) |
Write-back caching is allowed.
Definition at line 56 of file physmem_nommu.h.
Referenced by malloc().
| #define PHYS_MAP_WRBUF (0) |
| #define PHYS_MAP_WRTHROUGH (0) |
Write-through caching is allowed.
Definition at line 54 of file physmem_nommu.h.
| static void* physmem_map | ( | phys_addr_t | phys, | |
| phys_size_t | size, | |||
| unsigned long | flags | |||
| ) | [inline, static] |
Map a physical address to a virtual address.
This function returns a valid virtual address which can be used to access a given physical memory area with given access and caching properties.
| phys | A valid physical address. | |
| size | The size of the physical region to be mapped. | |
| flags | Flags specifying cache behaviour, etc. |
Definition at line 71 of file physmem_nommu.h.
Referenced by malloc().
| static void physmem_unmap | ( | void * | vaddr, | |
| phys_size_t | size | |||
| ) | [inline, static] |
Unmap a virtual-to-physical mapping.
This function cleans up any mappings set up by physmem_map(). It must be called when the virtual mapping isn't needed anymore.
| vaddr | A valid virtual address returned by physmem_map(). | |
| size | The size of the mapped region. |
Definition at line 86 of file physmem_nommu.h.


WITNESS LIST
Urban Affairs Committee
April 23, 2014 - 10:00 AM
Graffiti
On:
Bowers, Hollis (City of Corpus Christi Police Department)
Looney, Christopher (City of San Antonio)
Mckenzie, Lisa (City of san antonio)
Tipton, Katye (City of Houston)
Registering, but not testifying:
On:
Jones, James (San Antonio Police Dept.)
Joseph, Zenobia (Self)
Mangum, Henry (City of Corpus Christi Police Department)
Oversight of Agencies
On:
Garcia, Joe (TDHCA, Manufactured Housing)
Irvine, Tim (TDHCA)
Long, David (TSAHC)
Rutland, Tim (Texas commission on fire protection)
Registering, but not testifying:
On:
Joseph, Zenobia (Self)
Texas' Population Growth
On:
Dugan, John (City of san antonio)
Irvine, Tim (TDHCA)
Leffingwell, Lee (City Austin)
Tillotson, Gwendolyn (City of Houston)
Texas Coordinating Council for Veterans' Services
On:
Palladino, Thomas (Texas veterans commission)
Registering, but not testifying:
On:
Joseph, Zenobia (Self)
1


Wednesday 11th September 2019 Tickets | Schedule | Speakers | Sponsor | About / Contact Code of Conduct | Privacy Policy


6N/7D
Meet & greet on arrival at njp railway station / ixb airport & transfer to Gangtok. On arrival check-in to the hotel & rest or an overnight stay at Gangtok.
This morning start for a half-day trip to tsomgo lake (12400ft), which is only
32kms from Gangtok city, the lake is almost about 1 km long and 15 mtrs deep.
The lake is considered sacred by the local people, further 12kms visit the baba
Harbhajan Singh mandir. Evening free at Gangtok for shopping and individual
Activity. Night halt at Gangtok hotel.
This morning after breakfast visit Tashi view point, Ganesh Tak, hanuman tak
Flower show, do-dul Chorten, bakthang falls, Gunjan monastery, Banjakri
Falls. Night halt at Gangtok.
This morning after breakfast we will transfers you to darjeeling via melli
River rafting point, you can enjoy rafting at tees-ta river( own cost). Night
Halt at Darjeeling.
Early morning (at 04:00 am) drive to Tiger hill (8,400 ft.) To watch the
Spectacular sunrise over mt. Khangchendzongha (28,208 ft. Worlds 3rd highest
Peak), on your way back visit Batasia loop. After breakfast visit Himalayan
Mountaineering institute, p.n. zoological park (Thursday closed), Tenzing Rock,
Tibetan refugee self-help centre (Sunday closed), tea garden (outer view) and
Ropeway. Evening free for shopping or leisure. Overnight stay at Darjeeling.
Distance: 98 km travel time: 4 hours 10 minutes
After having morning breakfast we will take you to rock garden is also know
As barbotey rock garden, where you can find a natural waterfall, scenic view
Point. Narrow trekking point. You can visit Ganga Maya park, enjoy boating
( extra charges applicable), find some beautiful species of flowers, enjoy
Waterfalls etc after that back to the hotel. Evening back to Darjeeling.
Overnight stay at Darjeeling.
After breakfast check out of your hotel and travel back to njp/ixb for your
Onward journey. On the way visit mirik and Pashupati market (Nepal). As you go
Home let the everlasting memory of the radiant Himalayas and this beautiful
Serene kingdom linger in your mind and prompt you now and again to revisit
This place.


Lam-Alef and Kashida
Historical approach
Most fonts ligate lam+alef (for all relevant lam-like and alef-like characters) so it is a single glyph. Historically, SIL fonts did not do that but used separate lam and alef glyphs, contextually shaped to look like the shape of the traditional lam-alef ligature.
Amiri is another font that takes this approach and this note from one of the Amiri font’s fea files hints at potential problems:
# Kashida justification as implemented in most, if not all, applications is
# broken by design; it inserts kashidas *after* doing OT layout which makes it
# impossible for OT code to interact with those kashidas breaking all sorts of
# things.
One application that breaks is MS Word (at least 2013, 2016): it sometimes inserts a kashida between lam and alef when justifying text rendered in our fonts; the resulting rendering is completely unsuitable.
Amiri’s designer, Khaled Hosney, goes on to say how he fixed the problem:
# To trick LibreOffice/MS Office to not do kashida justification we set the
# default kashida to a zero width, blank glyph which makes them to think there
# is no suitable kashida glyph, resorting back to regular justification
# To get manually inserted kashida working we use an rlig feature to map to the
# actual kashida glyph(s).
Because Amiri has curved connections, and thus lots of different kashida glyphs (for different numbers of kashidas inserted), the fea logic is rather complex. For SIL fonts, with flat joins, the solution was much simpler: simply include both an encoded zero-width glyph, kashida-ar, and an unencoded non-zero width glyph, kashida-ar.haswidth, in our fonts. Then at some point in the fea/gdl, replace kashida-ar with kashida-ar.haswidth.
While this approach did prevent the lam-alef sequences from having visible kashidas inserted in them, it had a significant negative side effect: it prevented Word from using kashida justification where it was suitable.
Current strategy
In late 2020 we decided to move away from our existing strategy to one that implemented actual lam-alef ligature glyphs, which of course both fixes the problems and allows applications like Word to use kashida-based justfication. The status of our transition is as follows:
- Scheherazade: implemented in v3.000
- Lateef: implemented in v2.000
- Harmattan: implemented as of v4.000
- Alkalami: has always used ligature glyphs.
Exceptions:
While our strategy is to implement appropriate ligature glyphs for all relevant lam-like and alef-like characters, there is one exception: we have chosen to not create lam/alef ligature glyphs for U+0675 ARABIC LETTER HIGH HAMZA ALEF. This is for two reasons.
- Unicode has discouraged the use of alef with high hamza (U+0675) because the decomposition does not reflect the preferred order of representation.
- High hamza is only word initial and so it is unlikely that a lam+alef with high hamza would ever occur. Additionally, there is a terrible collision with the vertical position at which we have been asked to position the high hamza and it doesn’t seem worth trying to make it look right when it doesn’t occur in the real world.
- Unicode 14.0 encoded 19 new alef characters in the U+0870..U+0883 range. These characters are primarily quranic and it is mostly unknown when they might form a lam-alef ligature. Currently Scheherazade New v3.300 forms a lam-alef ligature with these characters only with a lam (U+0644) and not with any other lam-like characters. Our other fonts do not implement lam-alef ligatures with the alefs in the U+0870..U+0883 range.
Papers
This is an interesting paper that discusses ligatures (not just lam/alef and lam/lam/heh but other typographic ligatures). It’s a very old document, but it discusses some of the problems: Haralambous, Yannis. 1995. The traditional Arabic typecase extended to the Unicode set of glyphs


Petulant Meme
Storing a list of gifs couldn't be easier
{% csrf_token %} {{ form }}
Submit
Dude, you need to store gifs.
Add Some!
{% for url in urls %}
{% endfor %}


Prince Harry and Meghan Markle Looking for Tips on Having a Second Baby – Report
However much they may love parenthood, Harry and Meghan don’t want a castle full of kids and plan to have two, maximum – but a second baby announcement may be closer than anyone expects.
Royal well-wishers may start bracing for another round of baby news as Prince Harry and Meghan Markle have apparently displayed some interest in having a second child.
The Duke and Duchess of Sussex paid a surprise visit to British Army wives at a Windsor, UK event on Wednesday, and bonded with military families.
“Harry was really quite interested in how things were with second children because we both have older children,” military wife Susie Stringfellow told the state-run Forces Network, referring to herself and her friend.
“We were trying to encourage him to have a second baby,” she added with a chuckle.
Harry, 35, and Meghan, 38, welcomed their first-born and so far only child, Archie Harrison Mountbatten-Windsor, in May this year.
Another woman who was present recounted that “Harry was saying how little Archie was starting to crawl, how they've started eating different foods, [making] all of the funny faces.”
Speaking to British Vogue in July, Prince Harry revealed that he only wants two children “maximum”.
That same month, royal expert Katie Nicholl said in an interview with Entertainment Tonight that the pair are “loving parenthood” so much that they might be preparing for bringing in a sibling for Archie.
“I think it's probably a little premature to be speaking about a second baby,” Nicholl noted. “That said, sources close to the couple told me that they really would love to have a big family.”
She added there will possibly be a second pregnancy announcement for Meghan and Harry “sometime next year, but, for the moment, the focus is obviously on Archie.”


Home
Categories
About
Contact
Search
Search Companies
Search Ads
Search Jobs
Info
How it Works
Pricing
FAQ
Sign Up
Log in
Profile
Your Profile
Logout
Company Information
How many employees does your company have?
When was your company founded?
Briefly describe what service you want to offer?
Enter you business entity:
Partnership
Corporation
Proprietorship
About the company
Accept terms and conditions
Submit
Trusted by


Sri Satya Sai Hospital (3.0 KM) 080 2800 4600
Narayana Hospital (0.5 KM) 08071 112 555
Vydehi Hospital (3.5 KM) 080 2841 2956
Whitefield Police Station (5.0 KM)<PHONE_NUMBER>2
Kadugodi Police Station (5.0 KM)<PHONE_NUMBER>2
Mahadevapura fire station (4.7 KM)<PHONE_NUMBER>1
Praveen Kumar
Contact Number:
9886680441,
+91-80-61907512,
61906063,
3300,
1800 120 8858,
Email ID<EMAIL_ADDRESS>/<EMAIL_ADDRESS>Srinath B V
Contact Number:
9880304318,
91-80-61906061,
Email ID<EMAIL_ADDRESS>Vinay Rathore
Contact Number:
9999808880,
+91-80-40469389,
Email ID<EMAIL_ADDRESS>Sanjay
Contact Number:
7022026547,
Email ID<EMAIL_ADDRESS>Amit Ruhela
Contact Number:
7022034757,
Email ID<EMAIL_ADDRESS>Bhuvaneswaran
Contact Number:
9538216897,
91-80-61906062,
Email ID<EMAIL_ADDRESS>/<EMAIL_ADDRESS>One GE Helpdesk
Contact Number:
91-44-6632-6464 / Short Dial : 5000 / Toll Free: 1<PHONE_NUMBER>,
URL: http://helpdesk.ge.com
Ramesh Kauta
Contact Number:
9900072221 / 91-80-61906301
Email ID<EMAIL_ADDRESS>Contact Number:
91-80-61906000
Email ID<EMAIL_ADDRESS>Contact Number:
91-80-61906018
Contact Number:
91-80-61906064
Col Ajay Pal (AGM)
Contact Number:
91-9663424008
Email ID<EMAIL_ADDRESS>Map Location: Open Map
Yes, for the first week only. Please submit your parking needs by Nov 7th 2016 at http://surveys.ge.com/create/148279. You can collect your parking sticker from the facilities desk. Please contact<EMAIL_ADDRESS>/<PHONE_NUMBER>
It is inside the campus, pick up and drop is opposite to Tower-C building
Enter at Gate No. 2 of PSN Parking will be in MLCP2 (Multi Level Car Park) – Floors 5,6,7,8. You will have signs inside MLCP. Site Map: https://ge.box.com/s/f17viqvyb2lmaejw2yypb75ixnr7e0wf Please Note: Elevator C is only for service personnel. Employees are requested to use ONLY elevators - A & B. Employees can get to Tower-C from GND floor or skywalk on the first floor
No. You can avail only one of the two, as there are costs associated with each choice
You cannot use the car parking dangler for a two wheeler parking. For two wheelers we provide stickers. But there is paid parking available in MLCP
Overnight parking is NOT allowed. However, in case of exigency please notify Facilities at<EMAIL_ADDRESS>Metioned in the route link - https://ge.box.com/s/ltcxwfw57ysxqqkdr2hrwlgfo98ynxgj
PSN Bust Route Link: https://ge.box.com/s/ltcxwfw57ysxqqkdr2hrwlgfo98ynxgj
There are a variety of food options to choose from at PSN
1. GE Cafeteria: Ground Floor
- Kithchen Bells - 8:00 AM to 9:00 PM - Hot & cold snacks and fresh fruit juices
- HungerBox - 12:30 PM to 3:00 PM - Lunch ONLY
- Two Vending machines - 24x7 - Packaged drinks and snacks
2. Pantries (2) on each floor - tea / coffee vending machines & cookies
3. PSN Destination: Ground Floor (Opp to Tower-C)
- Multiple food counters with a variety of cuisines - 8:00 AM to 10:00 PM
No, all transactions will be through the food card. There are 2 types of food cards: a GE HungerBox food card that will be provided and a PSN Destination food card that can be purchased. GE food cards will be distributed on 7th Nov, at special counters set up on each floor. For the next 30 days, the cards can also be collected at a counter in the GE Cafeteria. Post the 30 day period, the cards can be picked up at the GE facilities desk, and employees will have to register the cards through the HungerBox app. You can recharge (top up) at the counter or via the Hungerbox app that has an integrated payment gateway for credit card / debit card / internet banking. The estimated wait times will be intimated through the App. Money transfer across food cards is not allowed. Also, GE food card cannot be used outside. Food has to be picked up at the cafeteria. Please note that food is not permitted in work areas
In case you forget to bring your food card, you can still pay at the Kitchen Bells or HungerBox counter through a QR Code scan from the HungerBox App. You can place the order either through web browser link or through the mobile app, and you will receive a QR code. Scan the QR Code at the counter, and payment will be deducted from your account. In case your food card gets lost, intimate hugerbox ASAP to deactivate the card immediately to safeguard the money on the card. Another card will be issued at a nominal charge and the amount will be transferred. The money on the food card will be refunded to the employee on returning the card.
All meeting rooms will be ready by Nov 30th on the 7th floor. In the meantime living spaces, pods, cabins, training and conference rooms can be leveraged. Rooms can be looked up by typing ~TP IN Bangalore HUB on outlook
For Day-1 and for first few weeks, we shall have an IT help desk available (look out for signage) on each floor to help in resolving any IT issues.
Please Click here to update the new Work/Office Number in GAL Directory
In case you need to add new Phone extension or need modification to your existing extension please raise a ticket at http://sc.ge.com/*myITassets .
In case you need any help with respect to your PC & Telephony please log a ticket with IT Helpdesk online @ http://helpdesk.ge.com or call at 5000 from office Desk-phone, this is important and mandatory to get desk side IT support as well.
We have introduced Condeco Solution as One Stop Solution for all Colloboration Rooms booking. Please Click here to refer the manual.
Please download & install Cisco Proximity Client from here to enable wireless projection in any of the POD/TP rooms. Post installation, click to open the proximity app from the task bar and it should automatically connect to the Cisco device. Refer to the tips in the app for more details. Note that Proximity feature should be up and running from 14-Nov
GE Digital Hub – India
Tower C, Ground - 7th Floor
Prestige Shantiniketan, Thigalarapalya, Hoodi,
Bengaluru, Karnataka – 560048
The 'Cerrato - follow me' print will be functional at the new office space
The Blue SSO will connect automatically. In case of any questions please reach out to the IT helpdesk on the floor
GE office has a medical room on the ground floor for emergencies<EMAIL_ADDRESS>PSN has a gym facility within the campus and GE employees can take the paid membership
Yes. They will follow the regular visiting management facility
Yes, we have a medical implant at Ground floor during office hours (9.00 am to 6.00 pm). Post office hours, GE reception holds the first aid box with them. Please reach out to<EMAIL_ADDRESS>/<PHONE_NUMBER>
Yes, PSN has a paid facility - 'Clay Day Care Center' within the Cresent building at the Prestige Shantiniketan Campus
Facilities First Level: Helpdesk 1800 120 8858
Facilities Second Level: Asst. Manager - Aneesh Kumar: +91 74600 45555
Facilities Fourth level: Reginal Manager - Praveen M Kumar: +91 98866 80441
Yes. Your current GE employee badges will suffice. If the employee does not have the GE badge a temporary one can be collected at the reception
There are multiple ATMs available near the Destination Food Court
Employee leaving office after 8.00 pm can opt for the Late Night drop. There will be an 8 pm drop & a 9.00 pm drop, employees will have to send an email to Facilites & Transport at least 2 hours before the schedule drop. Escort personnel will accompany if women employee's drop is the last one Please contact<EMAIL_ADDRESS>for any assistance
"Yes. Visitors are required to present a government issued ID and their GE host contact details. Upon verification they will be issued a visitors pass. Visitors can park his/her 4/2-wheeler at the paid visitor parking in MLCP. Visitors will need to be escorted at all times by the host. Host should reach out to GE reception/security in advance with visitor info at reception.psn<EMAIL_ADDRESS>GE other location employee must carry their GE ID card. GE ID card should be shown at security for his/her 4-wheeler/2 wheeler to be allowed inside They can use the GE parking slots if available, else they can avail the paid parking facility offered by PSN. They can get their badges activated for access from the security team in Tower-C.
Yes
Within the first week, Security/ facilities will be issuing the key at the desk. In future if you need the keys, a request needs to be raised in the OVSC tool @ https://ge.thepsc.com/Login.aspx
Please reach out to Stationery implant for the same. Email<EMAIL_ADDRESS>Ground floor
No
The Safe Assembly Area is on the right hand site of the Tower C
Ground Floor
Yes
Yes, HR will take care of this
New Joinee must carry Govt issued ID proof (Driving License, Voter ID, Aadhar card etc.) to enter Prestige Shantiniketan. New joinee will be given temp “T” cards at GE front office until their permanent badges are issued


|
Drake
|
#include <drake/geometry/shape_specification.h>
Public Member Functions | |
| ShapeName ()=default | |
| ShapeName (const Shape &shape) | |
Constructs a ShapeName from the given shape such that string() already contains the string representation of shape . More... | |
| std::string | name () const |
| Returns the name of the last shape reified. More... | |
Implementation of ShapeReifier interface | |
| void | ImplementGeometry (const Sphere &, void *) final |
| void | ImplementGeometry (const Cylinder &, void *) final |
| void | ImplementGeometry (const HalfSpace &, void *) final |
| void | ImplementGeometry (const Box &, void *) final |
| void | ImplementGeometry (const Capsule &, void *) final |
| void | ImplementGeometry (const Ellipsoid &, void *) final |
| void | ImplementGeometry (const Mesh &, void *) final |
| void | ImplementGeometry (const Convex &, void *) final |
| virtual void | ImplementGeometry (const Sphere &sphere, void *user_data) |
| virtual void | ImplementGeometry (const Cylinder &cylinder, void *user_data) |
| virtual void | ImplementGeometry (const HalfSpace &half_space, void *user_data) |
| virtual void | ImplementGeometry (const Box &box, void *user_data) |
| virtual void | ImplementGeometry (const Capsule &capsule, void *user_data) |
| virtual void | ImplementGeometry (const Ellipsoid &ellipsoid, void *user_data) |
| virtual void | ImplementGeometry (const Mesh &mesh, void *user_data) |
| virtual void | ImplementGeometry (const Convex &convex, void *user_data) |
| Public Member Functions inherited from ShapeReifier | |
| virtual | ~ShapeReifier ()=default |
Related Functions | |
(Note that these are not member functions.) | |
| std::ostream & | operator<< (std::ostream &out, const ShapeName &name) |
Additional Inherited Members | |
| Protected Member Functions inherited from ShapeReifier | |
| ShapeReifier ()=default | |
| virtual void | ThrowUnsupportedGeometry (const std::string &shape_name) |
| Derived ShapeReifiers can replace the default message for unsupported geometries by overriding this method. More... | |
| ShapeReifier (const ShapeReifier &)=default | |
| ShapeReifier & | operator= (const ShapeReifier &)=default |
| ShapeReifier (ShapeReifier &&)=default | |
| ShapeReifier & | operator= (ShapeReifier &&)=default |
|
default |
Constructs a ShapeName from the given shape
such that string()
already contains the string representation of shape
.
| virtual void ImplementGeometry |
| virtual void ImplementGeometry |
| virtual void ImplementGeometry |
| virtual void ImplementGeometry |
| virtual void ImplementGeometry |
| virtual void ImplementGeometry |
| virtual void ImplementGeometry |
| virtual void ImplementGeometry |
|
finalvirtual |
Reimplemented from ShapeReifier.
|
finalvirtual |
Reimplemented from ShapeReifier.
|
finalvirtual |
Reimplemented from ShapeReifier.
|
finalvirtual |
Reimplemented from ShapeReifier.
|
finalvirtual |
Reimplemented from ShapeReifier.
|
finalvirtual |
Reimplemented from ShapeReifier.
|
finalvirtual |
Reimplemented from ShapeReifier.
|
finalvirtual |
Reimplemented from ShapeReifier.
| std::string name | ( | ) | const |
Returns the name of the last shape reified.
Empty if no shape has been reified yet.
|
related |


Drink water throughout the day.
- Estimate how much water will be needed and decide who will obtain and check on water supplies.
- Guidelines recommend that outdoor workers drink 4 cups (8 cones) of water every hour, even if they’re not thirsty.
- It is best to drink a small amount of water often, like 1 cup (2 cones) every 15 minutes.
- Avoid alcohol and drinks with caffeine or sugar.
- Generally, fluid intake should not exceed 6 cups per hour.
Know what to do in an emergency. Have a plan in case a worker experiences heat-related illness. Everyone onsite should know the procedures for responding to possible heat illness:
- What steps to follow if a worker has signs of heat illness.
- Who to call for medical help and how to give clear directions to the worksite if calling 911.
- Who will provide first aid until the ambulance arrives.
Train workers before hot outdoor work begins. Tailor training to cover worksite-specific conditions. Address the following topics:
- Risk factors for heat-related illness.
- Different types of heat-related illness and how to recognize them.
- Heat-related illness prevention procedures, including drinking water.
- Importance of acclimatization and how your worksite procedures address it.
- The importance and method of responding to possible heat-related illness, including immediately reporting signs or symptoms to the supervisor.
- Procedures to follow when contacting emergency medical services, including providing clear directions to the worksite.
Pace the work and build up gradually to the heaviest work (called acclimatization). People can, to a large extent, adjust to heat. Some important reminders:
- New workers and those returning from an absence of two or more weeks should have a 5-day minimum adjustment period.
- Closely supervise new employees for the first 14 days or until they are fully acclimatized.
- Some workers require up to 2-3 weeks to fully acclimatize.
- Acclimatization is essential for all workers during a heat wave.
- When possible, allow only acclimatized workers to perform the more strenuous tasks.
Modify work/rest periods to give the body a chance to get rid of excess heat. Assign new and un-acclimatized workers lighter work and longer rest periods. Shorten work periods and increase rest periods:
- As temperature, humidity, and sunshine increase
- When there is no air movement or if protective clothing or gear is worn
- For heavier work
Monitor workers for signs and symptoms of heat illness.
- Check routinely to make sure workers are making use of water and shade and not experiencing heat-related symptoms.
- Monitor new workers and unacclimatized workers more closely.
- For workers wearing heavy or non-breathable clothing or during extreme heat conditions, check for physical signs (e.g., body temperature, heart rate) of possible over exposure to the heat.


Module: ActiveRecord::Associations::ClassMethods
| Defined in: |
Overview
Associations are a set of macro-like class methods for tying objects
together through foreign keys. They express relationships like “Project has
one Project Manager” or “Project belongs to a Portfolio”. Each macro adds a
number of methods to the class which are specialized according to the
collection or association symbol and the options hash. It works much the
same way as Ruby's own attr*
methods.
class Project < ActiveRecord::Base
belongs_to :portfolio
has_one :project_manager
has_many :milestones
has_and_belongs_to_many :categories
end
The project class now has the following methods (and more) to ease the traversal and manipulation of its relationships:
-
Project#portfolio, {Project#portfolio=(portfolio}), {Project#portfolio}.nil?
-
Project#project_manager, {Project#project_manager=(project_manager}), {Project#project_manager}.nil?,
-
Project#milestones.empty?, {Project#milestones}.size, {Project#milestones}, {Project#milestones<<(milestone}),
Project#milestones.delete(milestone), Project#milestones.destroy(milestone), Project#milestones.find(milestone_id),
Project#milestones.build, Project#milestones.create
-
Project#categories.empty?, {Project#categories}.size, {Project#categories}, {Project#categories<<(category1}),
Project#categories.delete(category1), Project#categories.destroy(category1)
A word of warning
Don't create associations that have the same name as instance methods
of ActiveRecord::Base
. Since the association adds a method
with that name to its model, it will override the inherited method and
break things. For instance, attributes
and
connection
would be bad choices for association names.
Auto-generated methods
See also Instance Public methods below for more details.
Singular associations (one-to-one)
| | belongs_to |
generated methods | belongs_to | :polymorphic | has_one
------------------------------------------------------------+---------
other(force_reload=false) | X | X | X
other=(other) | X | X | X
build_other(attributes={}) | X | | X
create_other(attributes={}) | X | | X
create_other!(attributes={}) | X | | X
Collection associations (one-to-many / many-to-many)
| | | has_many
generated methods | habtm | has_many | :through
---------------------------------------------------+----------
others(force_reload=false) | X | X | X
others=(other,other,...) | X | X | X
other_ids | X | X | X
other_ids=(id,id,...) | X | X | X
others<< | X | X | X
others.push | X | X | X
others.concat | X | X | X
others.build(attributes={}) | X | X | X
others.create(attributes={}) | X | X | X
others.create!(attributes={}) | X | X | X
others.size | X | X | X
others.length | X | X | X
others.count | X | X | X
others.sum(*args) | X | X | X
others.empty? | X | X | X
others.clear | X | X | X
others.delete(other,other,...) | X | X | X
others.delete_all | X | X | X
others.destroy(other,other,...) | X | X | X
others.destroy_all | X | X | X
others.find(*args) | X | X | X
others.exists? | X | X | X
others.distinct | X | X | X
others.uniq | X | X | X
others.reset | X | X | X
Overriding generated methods
Association methods are generated in a module that is included into the
model class, which allows you to easily override with your own methods and
call the original generated method with super
. For example:
class Car < ActiveRecord::Base
belongs_to :owner
belongs_to :old_owner
def owner=(new_owner)
self.old_owner = self.owner
super
end
end
If your model class is Project
, the module is named
Project::GeneratedFeatureMethods
. The GeneratedFeatureMethods
module is included in the model class immediately after the (anonymous)
generated attributes methods module, meaning an association will override
the methods for an attribute with the same name.
Cardinality and associations
Active Record associations can be used to describe one-to-one, one-to-many
and many-to-many relationships between models. Each model uses an
association to describe its role in the relation. The
belongs_to
association is always used in the model that has
the foreign key.
One-to-one
Use has_one
in the base, and belongs_to
in the
associated model.
class Employee < ActiveRecord::Base
has_one :office
end
class Office < ActiveRecord::Base
belongs_to :employee # foreign key - employee_id
end
One-to-many
Use has_many
in the base, and belongs_to
in the
associated model.
class Manager < ActiveRecord::Base
has_many :employees
end
class Employee < ActiveRecord::Base
belongs_to :manager # foreign key - manager_id
end
Many-to-many
There are two ways to build a many-to-many relationship.
The first way uses a has_many
association with the
:through
option and a join model, so there are two stages of
associations.
class Assignment < ActiveRecord::Base
belongs_to :programmer # foreign key - programmer_id
belongs_to :project # foreign key - project_id
end
class Programmer < ActiveRecord::Base
has_many :assignments
has_many :projects, through: :assignments
end
class Project < ActiveRecord::Base
has_many :assignments
has_many :programmers, through: :assignments
end
For the second way, use has_and_belongs_to_many
in both
models. This requires a join table that has no corresponding model or
primary key.
class Programmer < ActiveRecord::Base
has_and_belongs_to_many :projects # foreign keys in the join table
end
class Project < ActiveRecord::Base
has_and_belongs_to_many :programmers # foreign keys in the join table
end
Choosing which way to build a many-to-many relationship is not always
simple. If you need to work with the relationship model as its own entity,
use has_many :through
. Use
has_and_belongs_to_many
when working with legacy schemas or
when you never work directly with the relationship itself.
Is it a belongs_to
or has_one
association?
Both express a 1-1 relationship. The difference is mostly where to place
the foreign key, which goes on the table for the class declaring the
belongs_to
relationship.
class User < ActiveRecord::Base
# I reference an account.
belongs_to :account
end
class Account < ActiveRecord::Base
# One user references me.
has_one :user
end
The tables for these classes could look something like:
CREATE TABLE users (
id int(11) NOT NULL auto_increment,
account_id int(11) default NULL,
name varchar default NULL,
PRIMARY KEY (id)
)
CREATE TABLE accounts (
id int(11) NOT NULL auto_increment,
name varchar default NULL,
PRIMARY KEY (id)
)
Unsaved objects and associations
You can manipulate objects and associations before they are saved to the database, but there is some special behavior you should be aware of, mostly involving the saving of associated objects.
You can set the :autosave
option on a has_one
,
belongs_to
, has_many
, or
has_and_belongs_to_many
association. Setting it to
true
will always save the members, whereas setting it
to false
will never save the members. More details
about :autosave
option is available at AutosaveAssociation.
One-to-one associations
-
Assigning an object to a
has_one
association automatically saves that object and the object being replaced (if there is one), in order to update their foreign keys - except if the parent object is unsaved (new_record? == true
). -
If either of these saves fail (due to one of the objects being invalid), an
ActiveRecord::RecordNotSaved
exception is raised and the assignment is cancelled. -
If you wish to assign an object to a
has_one
association without saving it, use thebuild_association
method (documented below). The object being replaced will still be saved to update its foreign key. -
Assigning an object to a
belongs_to
association does not save the object, since the foreign key field belongs on the parent. It does not save the parent either.
Collections
-
Adding an object to a collection (
has_many
orhas_and_belongs_to_many
) automatically saves that object, except if the parent object (the owner of the collection) is not yet stored in the database. -
If saving any of the objects being added to a collection (via
push
or similar) fails, thenpush
returnsfalse
. -
If saving fails while replacing the collection (via
association=
), anActiveRecord::RecordNotSaved
exception is raised and the assignment is cancelled. -
You can add an object to a collection without automatically saving it by using the
collection.build
method (documented below). -
All unsaved (
new_record? == true
) members of the collection are automatically saved when the parent is saved.
Customizing the query
Associations are built from Relation
s, and you can use the
Relation
syntax to customize them. For example, to add a
condition:
class Blog < ActiveRecord::Base
has_many :published_posts, -> { where published: true }, class_name: 'Post'
end
Inside the -> { ... }
block you can use all of the usual
Relation
methods.
Accessing the owner object
Sometimes it is useful to have access to the owner object when building the query. The owner is passed as a parameter to the block. For example, the following association would find all events that occur on the user's birthday:
class User < ActiveRecord::Base
has_many :birthday_events, ->(user) { where starts_on: user.birthday }, class_name: 'Event'
end
Note: Joining, eager loading and preloading of these associations is not
fully possible. These operations happen before instance creation and the
scope will be called with a nil
argument. This can lead to
unexpected behavior and is deprecated.
Association callbacks
Similar to the normal callbacks that hook into the life cycle of an Active Record object, you can also define callbacks that get triggered when you add an object to or remove an object from an association collection.
class Project
has_and_belongs_to_many :developers, after_add: :evaluate_velocity
def evaluate_velocity(developer)
#...
end
end
It's possible to stack callbacks by passing them as an array. Example:
class Project
has_and_belongs_to_many :developers,
after_add: [:evaluate_velocity, Proc.new { |p, d| p.shipping_date = Time.now}]
end
Possible callbacks are: before_add
, after_add
,
before_remove
and after_remove
.
If any of the before_add
callbacks throw an exception, the
object will not be added to the collection.
Similarly, if any of the before_remove
callbacks throw an
exception, the object will not be removed from the collection.
Association extensions
The proxy objects that control the access to associations can be extended through anonymous modules. This is especially beneficial for adding new finders, creators, and other factory-type methods that are only used as part of this association.
class Account < ActiveRecord::Base
has_many :people do
def find_or_create_by_name(name)
first_name, last_name = name.split(" ", 2)
find_or_create_by(first_name: first_name, last_name: last_name)
end
end
end
person = Account.first.people.find_or_create_by_name("David Heinemeier Hansson")
person.first_name # => "David"
person.last_name # => "Heinemeier Hansson"
If you need to share the same extensions between many associations, you can use a named extension module.
module FindOrCreateByNameExtension
def find_or_create_by_name(name)
first_name, last_name = name.split(" ", 2)
find_or_create_by(first_name: first_name, last_name: last_name)
end
end
class Account < ActiveRecord::Base
has_many :people, -> { extending FindOrCreateByNameExtension }
end
class Company < ActiveRecord::Base
has_many :people, -> { extending FindOrCreateByNameExtension }
end
Some extensions can only be made to work with knowledge of the
association's internals. Extensions can access relevant state using the
following methods (where items
is the name of the
association):
-
record.association(:items).owner
- Returns the object the association is part of. -
record.association(:items).reflection
- Returns the reflection object that describes the association. -
record.association(:items).target
- Returns the associated object forbelongs_to
andhas_one
, or the collection of associated objects forhas_many
andhas_and_belongs_to_many
.
However, inside the actual extension code, you will not have access to the
record
as above. In this case, you can access
proxy_association
. For example,
record.association(:items)
and
record.items.proxy_association
will return the same object,
allowing you to make calls like proxy_association.owner
inside
association extensions.
Association Join Models
Has Many associations can be configured with the :through
option to use an explicit join model to retrieve the data. This operates
similarly to a has_and_belongs_to_many
association. The
advantage is that you're able to add validations, callbacks, and extra
attributes on the join model. Consider the following schema:
class Author < ActiveRecord::Base
has_many :authorships
has_many :books, through: :authorships
end
class Authorship < ActiveRecord::Base
belongs_to :author
belongs_to :book
end
@author = Author.first
@author..collect { |a| a.book } # selects all books that the author's authorships belong to
@author.books # selects all books by using the Authorship join model
You can also go through a has_many
association on the join
model:
class Firm < ActiveRecord::Base
has_many :clients
has_many :invoices, through: :clients
end
class Client < ActiveRecord::Base
belongs_to :firm
has_many :invoices
end
class Invoice < ActiveRecord::Base
belongs_to :client
end
@firm = Firm.first
@firm.clients.flat_map { |c| c.invoices } # select all invoices for all clients of the firm
@firm.invoices # selects all invoices by going through the Client join model
Similarly you can go through a has_one
association on the join
model:
class Group < ActiveRecord::Base
has_many :users
has_many :avatars, through: :users
end
class User < ActiveRecord::Base
belongs_to :group
has_one :avatar
end
class Avatar < ActiveRecord::Base
belongs_to :user
end
@group = Group.first
@group.users.collect { |u| u.avatar }.compact # select all avatars for all users in the group
@group.avatars # selects all avatars by going through the User join model.
An important caveat with going through has_one
or
has_many
associations on the join model is that these
associations are read-only. For example, the following
would not work following the previous example:
@group.avatars << Avatar.new # this would work if User belonged_to Avatar rather than the other way around
<EMAIL_ADDRESS># so would this
Setting Inverses
If you are using a belongs_to
on the join model, it is a good
idea to set the :inverse_of
option on the
belongs_to
, which will mean that the following example works
correctly (where tags
is a has_many
:through
association):
@post = Post.first
@tag = @post..build name: "ruby"
@tag.save
The last line ought to save the through record (a Taggable
).
This will only work if the :inverse_of
is set:
class Taggable < ActiveRecord::Base
belongs_to :post
belongs_to :tag, inverse_of: :taggings
end
If you do not set the :inverse_of
record, the association will
do its best to match itself up with the correct inverse. Automatic inverse
detection only works on has_many
, has_one
, and
belongs_to
associations.
Extra options on the associations, as defined in the
AssociationReflection::INVALID_AUTOMATIC_INVERSE_OPTIONS
constant, will also prevent the association's inverse from being found
automatically.
The automatic guessing of the inverse association uses a heuristic based on the name of the class, so it may not work for all associations, especially the ones with non-standard names.
You can turn off the automatic detection of inverse associations by setting
the :inverse_of
option to false
like so:
class Taggable < ActiveRecord::Base
belongs_to :tag, inverse_of: false
end
Nested Associations
You can actually specify any association with the
:through
option, including an association which has a
:through
option itself. For example:
class Author < ActiveRecord::Base
has_many :posts
has_many :comments, through: :posts
has_many :commenters, through: :comments
end
class Post < ActiveRecord::Base
has_many :comments
end
class Comment < ActiveRecord::Base
belongs_to :commenter
end
@author = Author.first
@author.commenters # => People who commented on posts written by the author
An equivalent way of setting up this association this would be:
class Author < ActiveRecord::Base
has_many :posts
has_many :commenters, through: :posts
end
class Post < ActiveRecord::Base
has_many :comments
has_many :commenters, through: :comments
end
class Comment < ActiveRecord::Base
belongs_to :commenter
end
When using a nested association, you will not be able to modify the
association because there is not enough information to know what
modification to make. For example, if you tried to add a
Commenter
in the example above, there would be no way to tell
how to set up the intermediate Post
and Comment
objects.
Polymorphic Associations
Polymorphic associations on models are not restricted on what types of
models they can be associated with. Rather, they specify an interface that
a has_many
association must adhere to.
class Asset < ActiveRecord::Base
belongs_to :attachable, polymorphic: true
end
class Post < ActiveRecord::Base
has_many :assets, as: :attachable # The :as option specifies the polymorphic interface to use.
end
@asset.attachable = @post
This works by using a type column in addition to a foreign key to specify
the associated record. In the Asset example, you'd need an
attachable_id
integer column and an
attachable_type
string column.
Using polymorphic associations in combination with single table inheritance
(STI) is a little tricky. In order for the associations to work as
expected, ensure that you store the base model for the STI models in the
type column of the polymorphic association. To continue with the asset
example above, suppose there are guest posts and member posts that use the
posts table for STI. In this case, there must be a type
column
in the posts table.
Note: The attachable_type=
method is being called when
assigning an attachable
. The class_name
of the
attachable
is passed as a String.
class Asset < ActiveRecord::Base
belongs_to :attachable, polymorphic: true
def attachable_type=(class_name)
super(class_name.constantize.base_class.to_s)
end
end
class Post < ActiveRecord::Base
# because we store "Post" in attachable_type now dependent: :destroy will work
has_many :assets, as: :attachable, dependent: :destroy
end
class GuestPost < Post
end
class MemberPost < Post
end
Caching
All of the methods are built on a simple caching principle that will keep the result of the last query around unless specifically instructed not to. The cache is even shared across methods to make it even cheaper to use the macro-added methods without worrying too much about performance at the first go.
project.milestones # fetches milestones from the database
project.milestones.size # uses the milestone cache
project.milestones.empty? # uses the milestone cache
project.milestones(true).size # fetches milestones from the database
project.milestones # uses the milestone cache
Eager loading of associations
Eager loading is a way to find objects of a certain class and a number of named associations. It is one of the easiest ways to prevent the dreaded N+1 problem in which fetching 100 posts that each need to display their author triggers 101 database queries. Through the use of eager loading, the number of queries will be reduced from 101 to 2.
class Post < ActiveRecord::Base
belongs_to :author
has_many :comments
end
Consider the following loop using the class above:
Post.all.each do |post|
puts "Post: " + post.title
puts "Written by: " + post..name
puts "Last comment on: " + post.comments.first.created_on
end
To iterate over these one hundred posts, we'll generate 201 database queries. Let's first just optimize it for retrieving the author:
Post.includes(:author).each do |post|
This references the name of the belongs_to
association that
also used the :author
symbol. After loading the posts, find
will collect the author_id
from each one and load all the
referenced authors with one query. Doing so will cut down the number of
queries from 201 to 102.
We can improve upon the situation further by referencing both associations in the finder with:
Post.includes(:author, :comments).each do |post|
This will load all comments with a single query. This reduces the total
number of queries to 3. In general, the number of queries will be 1 plus
the number of associations named (except if some of the associations are
polymorphic belongs_to
- see below).
To include a deep hierarchy of associations, use a hash:
Post.includes(:author, { comments: { author: :gravatar } }).each do |post|
The above code will load all the comments and all of their associated authors and gravatars. You can mix and match any combination of symbols, arrays, and hashes to retrieve the associations you want to load.
All of this power shouldn't fool you into thinking that you can pull out huge amounts of data with no performance penalty just because you've reduced the number of queries. The database still needs to send all the data to Active Record and it still needs to be processed. So it's no catch-all for performance problems, but it's a great way to cut down on the number of queries in a situation as the one described above.
Since only one table is loaded at a time, conditions or orders cannot reference tables other than the main one. If this is the case, Active Record falls back to the previously used LEFT OUTER JOIN based strategy. For example:
Post.includes([:author, :comments]).where(['comments.approved = ?', true])
This will result in a single SQL query with joins along the lines of:
LEFT OUTER JOIN comments ON comments.post_id = posts.id
and
LEFT OUTER JOIN authors ON authors.id = posts.author_id
. Note
that using conditions like this can have unintended consequences. In the
above example posts with no approved comments are not returned at all,
because the conditions apply to the SQL statement as a whole and not just
to the association.
You must disambiguate column references for this fallback to happen, for
example order: "author.name DESC"
will work but
order: "name DESC"
will not.
If you want to load all posts (including posts with no approved comments) then write your own LEFT OUTER JOIN query using ON
Post.joins("LEFT OUTER JOIN comments ON comments.post_id = posts.id AND comments.approved = '1'")
In this case it is usually more natural to include an association which has conditions defined on it:
class Post < ActiveRecord::Base
has_many :approved_comments, -> { where approved: true }, class_name: 'Comment'
end
Post.includes(:approved_comments)
This will load posts and eager load the approved_comments
association, which contains only those comments that have been approved.
If you eager load an association with a specified :limit
option, it will be ignored, returning all the associated objects:
class Picture < ActiveRecord::Base
has_many :most_recent_comments, -> { order('id DESC').limit(10) }, class_name: 'Comment'
end
Picture.includes(:most_recent_comments).first.most_recent_comments # => returns all associated comments.
Eager loading is supported with polymorphic associations.
class Address < ActiveRecord::Base
belongs_to :addressable, polymorphic: true
end
A call that tries to eager load the addressable model
Address.includes(:addressable)
This will execute one query to load the addresses and load the addressables
with one query per addressable type. For example if all the addressables
are either of class Person or Company then a total of 3 queries will be
executed. The list of addressable types to load is determined on the back
of the addresses loaded. This is not supported if Active Record has to
fallback to the previous implementation of eager loading and will raise
ActiveRecord::EagerLoadPolymorphicError
. The reason is that
the parent model's type is a column value so its corresponding table
name cannot be put in the FROM
/JOIN
clauses of
that query.
Table Aliasing
Active Record uses table aliasing in the case that a table is referenced
multiple times in a join. If a table is referenced only once, the standard
table name is used. The second time, the table is aliased as
#{reflection_name}_#{parent_table_name}
. Indexes are appended
for any more successive uses of the table name.
Post.joins(:comments)
# => SELECT ... FROM posts INNER JOIN comments ON ...
Post.joins(:special_comments) # STI
# => SELECT ... FROM posts INNER JOIN comments ON ... AND comments.type = 'SpecialComment'
Post.joins(:comments, :special_comments) # special_comments is the reflection name, posts is the parent table name
# => SELECT ... FROM posts INNER JOIN comments ON ... INNER JOIN comments special_comments_posts
Acts as tree example:
TreeMixin.joins(:children)
# => SELECT ... FROM mixins INNER JOIN mixins childrens_mixins ...
TreeMixin.joins(children: :parent)
# => SELECT ... FROM mixins INNER JOIN mixins childrens_mixins ...
INNER JOIN parents_mixins ...
TreeMixin.joins(children: {parent: :children})
# => SELECT ... FROM mixins INNER JOIN mixins childrens_mixins ...
INNER JOIN parents_mixins ...
INNER JOIN mixins childrens_mixins_2
Has and Belongs to Many join tables use the same idea, but add a
_join
suffix:
Post.joins(:categories)
# => SELECT ... FROM posts INNER JOIN categories_posts ... INNER JOIN categories ...
Post.joins(categories: :posts)
# => SELECT ... FROM posts INNER JOIN categories_posts ... INNER JOIN categories ...
INNER JOIN categories_posts posts_categories_join INNER JOIN posts posts_categories
Post.joins(categories: {posts: :categories})
# => SELECT ... FROM posts INNER JOIN categories_posts ... INNER JOIN categories ...
INNER JOIN categories_posts posts_categories_join INNER JOIN posts posts_categories
INNER JOIN categories_posts categories_posts_join INNER JOIN categories categories_posts_2
If you wish to specify your own custom joins using joins
method, those table names will take precedence over the eager associations:
Post.joins(:comments).joins("inner join comments ...")
# => SELECT ... FROM posts INNER JOIN comments_posts ON ... INNER JOIN comments ...
Post.joins(:comments, :special_comments).joins("inner join comments ...")
# => SELECT ... FROM posts INNER JOIN comments comments_posts ON ...
INNER JOIN comments special_comments_posts ...
INNER JOIN comments ...
Table aliases are automatically truncated according to the maximum length of table identifiers according to the specific database.
Modules
By default, associations will look for objects within the current module scope. Consider:
module MyApplication
module Business
class Firm < ActiveRecord::Base
has_many :clients
end
class Client < ActiveRecord::Base; end
end
end
When Firm#clients
is called, it will in turn call
MyApplication::Business::Client.find_all_by_firm_id(firm.id)
.
If you want to associate with a class in another module scope, this can be
done by specifying the complete class name.
module MyApplication
module Business
class Firm < ActiveRecord::Base; end
end
module Billing
class Account < ActiveRecord::Base
belongs_to :firm, class_name: "MyApplication::Business::Firm"
end
end
end
Bi-directional associations
When you specify an association there is usually an association on the associated model that specifies the same relationship in reverse. For example, with the following models:
class Dungeon < ActiveRecord::Base
has_many :traps
has_one :evil_wizard
end
class Trap < ActiveRecord::Base
belongs_to :dungeon
end
class EvilWizard < ActiveRecord::Base
belongs_to :dungeon
end
The traps
association on Dungeon
and the
dungeon
association on Trap
are the inverse of
each other and the inverse of the dungeon
association on
EvilWizard
is the evil_wizard
association on
Dungeon
(and vice-versa). By default, Active Record
doesn't know anything about these inverse relationships and so no
object loading optimization is possible. For example:
d = Dungeon.first
t = d.traps.first
d.level == t.dungeon.level # => true
d.level = 10
d.level == t.dungeon.level # => false
The Dungeon
instances d
and
t.dungeon
in the above example refer to the same object data
from the database, but are actually different in-memory copies of that
data. Specifying the :inverse_of
option on associations lets
you tell Active Record about inverse relationships and it will optimise
object loading. For example, if we changed our model definitions to:
class Dungeon < ActiveRecord::Base
has_many :traps, inverse_of: :dungeon
has_one :evil_wizard, inverse_of: :dungeon
end
class Trap < ActiveRecord::Base
belongs_to :dungeon, inverse_of: :traps
end
class EvilWizard < ActiveRecord::Base
belongs_to :dungeon, inverse_of: :evil_wizard
end
Then, from our code snippet above, d
and
t.dungeon
are actually the same in-memory instance and our
final d.level == t.dungeon.level
will return
true
.
There are limitations to :inverse_of
support:
-
does not work with
:through
associations. -
does not work with
:polymorphic
associations. -
for
belongs_to
associationshas_many
inverse associations are ignored.
Deleting from associations
Dependent associations
has_many
, has_one
and belongs_to
associations support the :dependent
option. This allows you to
specify that associated records should be deleted when the owner is
deleted.
For example:
class Author
has_many :posts, dependent: :destroy
end
Author.find(1).destroy # => Will destroy all of the author's posts, too
The :dependent
option can have different values which specify
how the deletion is done. For more information, see the documentation for
this option on the different specific association types. When no option is
given, the behavior is to do nothing with the associated records when
destroying a record.
Note that :dependent
is implemented using Rails' callback
system, which works by processing callbacks in order. Therefore, other
callbacks declared either before or after the :dependent
option can affect what it does.
Delete or destroy?
has_many
and has_and_belongs_to_many
associations
have the methods destroy
, delete
,
destroy_all
and delete_all
.
For has_and_belongs_to_many
, delete
and
destroy
are the same: they cause the records in the join table
to be removed.
For has_many
, destroy
and
destroy_all
will always call the destroy
method
of the record(s) being removed so that callbacks are run. However
delete
and delete_all
will either do the deletion
according to the strategy specified by the :dependent
option,
or if no :dependent
option is given, then it will follow the
default strategy. The default strategy is to do nothing (leave the foreign
keys with the parent ids set), except for has_many
:through
, where the default strategy is
delete_all
(delete the join records, without running their
callbacks).
There is also a clear
method which is the same as
delete_all
, except that it returns the association rather than
the records which have been deleted.
What gets deleted?
There is a potential pitfall here: has_and_belongs_to_many
and
has_many
:through
associations have records in
join tables, as well as the associated records. So when we call one of
these deletion methods, what exactly should be deleted?
The answer is that it is assumed that deletion on an association is about
removing the link between the owner and the associated object(s),
rather than necessarily the associated objects themselves. So with
has_and_belongs_to_many
and has_many
:through
, the join records will be deleted, but the associated
records won't.
This makes sense if you think about it: if you were to call
post.tags.delete(Tag.find_by(name: 'food'))
you would
want the 'food' tag to be unlinked from the post, rather than for
the tag itself to be removed from the database.
However, there are examples where this strategy doesn't make sense. For
example, suppose a person has many projects, and each project has many
tasks. If we deleted one of a person's tasks, we would probably not
want the project to be deleted. In this scenario, the delete method
won't actually work: it can only be used if the association on the join
model is a belongs_to
. In other situations you are expected to
perform operations directly on either the associated records or the
:through
association.
With a regular has_many
there is no distinction between the
“associated records” and the “link”, so there is only one choice for what
gets deleted.
With has_and_belongs_to_many
and has_many
:through
, if you want to delete the associated records
themselves, you can always do something along the lines of
person.tasks.each(&:destroy)
.
Type safety with ActiveRecord::AssociationTypeMismatch
If you attempt to assign an object to an association that doesn't match
the inferred or specified :class_name
, you'll get an
ActiveRecord::AssociationTypeMismatch
.
Options
All of the association macros can be specialized through options. This makes cases more complex than the simple and guessable ones possible.


Normalizes menu to a consistent array
normMenu(menu, [obj]);
| menu |
array, object, or function, array of items to normalize |
| obj |
object, Object |
This function is used in all the menus to normalized to an array of objects { id, text }. For example
returns
It can also be an object
returns


Course Information
Instructor: Carrie Gardner
Class: 6-8:50PM Thurs
Office Hours: 5PM Thurs.
This course covers issues related to administration and management of security of enterprise information systems and networks. Topics include intrusion detection systems, vulnerability analysis, anomaly detection, computer forensics, application logging, auditing and data management, risk management, contingency planning and incident handling, cyber defense/operations, and security program management and lifecyle. The course will study in detail principles and tools related to these topics. The course will also cover security standards, evaluation, accreditation and certification process; security planning, compliance issues ethical and legal issues in information; privacy, traceability and cyber-evidence
The course is aimed at imparting knowledge and skill sets required to assume the overall responsibilities of administration and management of security of an enterprise information system. The course is aimed at developing capabilities to do the following:
Reading Material
There is no one textbook that covers all of the material for the course. I will use two primary books which are required, and will provide electronic references for other material.Exercise Equipment


Supervise is the easiest way for supervisors to track their student's work—and get results.
Supervise allows you to manage all of your students in one place, It’s the only comprehensive tool that eliminates extra work and simplifies everything from communication with real-time project supervision to project tracking and reporting, both for students and supervisors.
Easy communication between students and supervisors.
Organized Meetings and Activities.
Print supervision and activities forms easily at will.
Not a single file gets lost with Supervise. All the student's and supervisor's data are secured, and back-up is available. Plus, You can archieve your data as much as you want !
Find the right supervisor or student for you. Gain insights with Supervise, view other supervisors field of experty and performance.
Access Supervise from anywhere with any device ! You can access it from all of your devices, after and important meeting, or on plane to a conference.
Let us show you how Supervise works.


A-Frame Physics Examples
by Don McCurdy (
@donrmccurdy
)
Repo
A-Frame Physics System
Source repo for the actual A-Frame VR `aframe-physics-system` component built on CANNON.js.
Code for Physics Examples
Glitch.com code that hosts these aframe physics examples
Examples
Scene
Tags
Awesome
Stress
controls, force, impulse
✅
Sweeper
collider, dynamic-body, velocity
✅
Constraints
constraint, hinge, lock
✅
Hinge with model
constraint, hinge
✅
Orange shooter
force, velocity, controls
✅


Toggle navigation
Rule Generator
Reset
Submit
Rule Name:
True Event :
False Event:
Trigger:
Append Numerical


--- title: Sponsors linkTitle: "sponsors" aliases: [ "/pt-br/sponsors/", "/zh-cn/sponsors/", "/ja/sponsors/", "/other/sponsors/", ] --- {{< blocks/cover title="Sponsors" image_anchor="top" height="min" color="selenium-purple">}}
The following companies have sponsored the Selenium project. We thank each and every one of them for their generous support.
{{< /blocks/cover >}}


QMRITools PACKAGE SYMBOL
SequenceSpaceEcho
SequenceSpaceEcho[din, H, t$1, t$2, necho, b$1]
performs a multi echo spin echo experiment with a 90 degree spin echo, with t1 the time between the 90 degree RF pulse and the first 180 degree RF pulse, t2 the time betwteen a 180 degree RF pulse and the following readout (and 2xt1 the time between two consecutive 180 degree RF pulses. Further defines necho the number of 180 degree RF pulses, din the spin system given the hamiltonian H using b1. The t1 and t2 are defined in ms, and b1 of 100% is defines as 1. The output is a new spinsystem dout


Nagios is a popular monitoring framework for distributed hosts. This guide explains how to monitor a DC/OS cluster with Nagios Core 4x using NRPE.
Installation
This guide assumes you’ve installed and configured Nagios for your cluster. Below are links to popular configuration management suites to help with that.
- Puppet Module: thias/nagios
- Chef Cookbook: schubergphilis/nagios
- Manual Install: Good Luck!
Recommendations
- Use SSL
The NRPE plugin for Nagios allows you to setup this server-daemon interface with SSL. We recommend you do this for security.
- Lightweight Checks
Nagios is a great tool, but don’t overload your check scripts. The most common Nagios implementation error is building overly complicated scripts, and not paying attention to resource consumption the check requires. This could undermine your cluster performance. Ensure your checks are clean, require low resource overhead and make full use of the process in which they’re spawned (i.e., don’t pipe grep to awk).
- Nagios via DC/OS
We do not recommend running Nagios via DC/OS. There are popular containers to run Nagios, and you can theoretically run Nagios on DC/OS via one of these containers.
However, guaranteeing that DC/OS will spawn the container on every host correctly is tricky, and if the thing you’re monitoring is also responsible for running your monitoring platform, you’ll most likely end up a sad operator when that thing goes down, since your monitoring platform will die with it.
What to Monitor
Once you have Nagios installed on your cluster and have the NRPE plugin configured then you can begin to construct scripts to monitor resource health for DC/OS.
systemd units
DC/OS runs only on systemd. Tracking units with Nagios is easy. You can use one of the popular scripts for NRPE remote checks such as jonschipp/nagios-plugins/check_service.sh or roll your own.
Units differ between agent’s and master’s, but you can easily determine which units to monitor without hard coding these (since they are prone to changing or being added to). We can modify jonschipp/nagios-plugins/check_service.sh for monitoring only DC/OS units by adding a simple wrapper:
1 2 3 4 5 6 7 8 9 10 11 |
|
If a service is not healthy, such as adminrouter, we will get a failure from this script:
1 2 3 |
|
Docker
Monitoring Docker via Nagios can be tricky, as there are many aspects you might want to watch. If your intent is to monitor the service is available and running, (i.e., Docker service is running and enabled and healthy according to systemd) then we recommend a NRPE script that does just that.
If your intent is to monitor what is going on inside the container, we recommend you run a service such as cAdvisor.


Base class for all message containers.
More...
#include </Users/howes/src/sidecar/Messages/Message.h>
Base class for all message containers.
Implements the same interface as BaseMessageImpl, but simply forwards requests to the held BaseMessageImpl object. Type-specific Derived classes must define getMessageMetaTypeInfo() to return the type-specific meta data.
Definition at line 20 of file Message.h.
| SideCar::Messages::BaseMessage::BaseMessage |
( |
| ) |
|
|
inline |
Default constructor.
Creates a 'null' instance with no backing implementation.
Definition at line 27 of file Message.h.
Constructor.
Restrict access to derived classes in order to guarantee type-safety while using getImpl() type-cast methods.
- Parameters
-
| impl | implementation object to use for data |
Definition at line 116 of file Message.h.
| Time::TimeStamp SideCar::Messages::BaseMessage::getMessageCreatedTimeStamp |
( |
| ) |
const |
|
inline |
| Time::TimeStamp SideCar::Messages::BaseMessage::getMessageEmittedTimeStamp |
( |
| ) |
const |
|
inline |
Obtain the time when this message was emitted to a network device.
Useful in identifying latencies among nodes.
- Returns
- Time::TimeStamp value
Definition at line 77 of file Message.h.
Obtain meta data that describes the message type.
Derived classes must implement.
- Returns
- reference to Messages::MetaTypeInfo object
Definition at line 39 of file Message.h.
| const std::string& SideCar::Messages::BaseMessage::getMessageProducer |
( |
| ) |
const |
|
inline |
Obtain the name of the entity that created this message; usually the name of an algorithm.
- Returns
- creator name
Definition at line 46 of file Message.h.
| uint32_t SideCar::Messages::BaseMessage::getMessageSequenceNumber |
( |
| ) |
const |
|
inline |
Obtain the sequence number associated with this message.
- Returns
- sequence number
Definition at line 52 of file Message.h.
| size_t SideCar::Messages::BaseMessage::getMessageSize |
( |
| ) |
const |
|
inline |
Obtain the number of bytes occupied by this message.
- Returns
- byte count
Definition at line 83 of file Message.h.
template<typename T >
| T& SideCar::Messages::BaseMessage::getTImpl |
( |
| ) |
|
|
inlineprotected |
Template type-cast operator to obtain a modifiable reference type derived from BaseMessageImpl.
NOTE: should cause code to abort if the held pointer is NULL.
- Returns
- modifiable reference to held object of type T
Definition at line 124 of file Message.h.
template<typename T >
| const T& SideCar::Messages::BaseMessage::getTImpl |
( |
| ) |
const |
|
inlineprotected |
Template type-cast operator to obtain a read-only reference type derived from BaseMessageImpl.
NOTE: should cause code to abort if the held pointer is NULL.
- Returns
- read-only reference to held object of type T
Definition at line 132 of file Message.h.
| bool SideCar::Messages::BaseMessage::isValid |
( |
| ) |
const |
|
inline |
Determine if there is a valid backing object present.
- Returns
- true if so
Definition at line 33 of file Message.h.
| ACE_InputCDR& SideCar::Messages::BaseMessage::load |
( |
ACE_InputCDR & |
cdr | ) |
|
|
inline |
Update attribute values using data from an ACE input CDR object.
- Parameters
-
- Returns
- reference to given ACE_InputCDR object
Definition at line 91 of file Message.h.
| std::ostream& SideCar::Messages::BaseMessage::print |
( |
std::ostream & |
os | ) |
const |
|
inline |
Write out a textual representation of the object to the given stream.
- Parameters
-
| os | the C++ output stream to write to |
- Returns
- reference to given output stream
Definition at line 107 of file Message.h.
| void SideCar::Messages::BaseMessage::setMessageCreatedTimeStamp |
( |
const Time::TimeStamp & |
value | ) |
|
|
inline |
Set the time when this message was created.
- Parameters
-
Definition at line 70 of file Message.h.
| void SideCar::Messages::BaseMessage::setMessageSequenceNumber |
( |
uint32_t |
value | ) |
|
|
inline |
Set the sequence number associated with this message.
- Parameters
-
| value | new sequence number to use |
Definition at line 58 of file Message.h.
| ACE_OutputCDR& SideCar::Messages::BaseMessage::write |
( |
ACE_OutputCDR & |
cdr | ) |
const |
|
inline |
Store attribute values into an ACE output CDR object.
- Parameters
-
- Returns
- reference to given ACE_OutputCDR object
Definition at line 99 of file Message.h.
The documentation for this class was generated from the following file:


Dev Edmonton Society’s mission is to build an impactful, diverse, and collaborative developer community. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, religion (or lack thereof) and any personal characteristics protected under the Alberta Human Rights Act.
This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
We invite all those who participate in Dev Edmonton Society to help us create safe and positive experiences for everyone.
A supplemental goal of this Code of Conduct is to increase open culture citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.
Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society.
If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know.
The following behaviors are expected and requested of all community members:
The following behaviors are considered harassment and are unacceptable within our community:
Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated.
In an effort to build a more collaborative and inclusive community, we always endevour to resolve disputes and conduct violations through education, dialog, and respectful communication. People who demonstrate a sincere effort to change behaviour will be given a reasonable opportunity to do so, and having done so to participate in the community, but continued violations will not be tolerated and may result in further actions at the discretion of the community organizers.
Anyone asked to stop unacceptable behavior is expected to comply immediately.
If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event).
If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible<EMAIL_ADDRESS>Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.
We expect all community participants (people, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues–online and in-person–as well as in all one-on-one communications pertaining to community business.
This code of conduct and its related procedures also applies to unacceptable behavior occurring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members.
No weapons are allowed at Dev Edmonton Society events or events of the groups it’s supports, including but not limited to explosives (including fireworks), guns, and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon.
Attendees are further expected to comply with all provincial and local laws on this matter.
<EMAIL_ADDRESS>This Code of Conduct is distributed under a Creative Commons Attribution-ShareAlike license.
Portions of text derived from the Django Code of Conduct and the Geek Feminism Anti-Harassment Policy.
Retrieved on November 22, 2016 from http://citizencodeofconduct.org/


JavaScript is disabled on your browser.
Overview
Package
Class
Use
Tree
Deprecated
Index
Help
Prev Letter
Next Letter
Frames
No Frames
All Classes
A
B
C
D
E
F
G
H
I
J
L
M
N
O
P
R
S
T
U
V
W
X
Y
C
CELESTIAL
- Static variable in class net.co.java.skill.
Skill
chance(int)
- Method in class net.co.java.skill.
Skill.PassiveSkill
chance(int)
- Method in class net.co.java.skill.
Snow
Character_Creation_Packet
- Class in
net.co.java.packets
Character_Creation_Packet(IncomingPacket)
- Constructor for class net.co.java.packets.
Character_Creation_Packet
characterInformation()
- Method in class net.co.java.entity.
Player
classReq
- Variable in class net.co.java.item.
ItemPrototype.EquipmentPrototype
close()
- Method in class net.co.java.server.
AbstractClient
Close this
Client
close()
- Method in class net.co.java.server.
AbstractServer
close()
- Method in class net.co.java.server.
Server
close()
- Method in class net.co.java.server.
ServerThread
Close the connection for this
Socket
.
Command
- Class in
net.co.java.server
Command(MessagePacket)
- Constructor for class net.co.java.server.
Command
contains(Entity)
- Method in class net.co.java.entity.
Entity.View
Check if the View contains a specific Entity
contains(ItemInstance)
- Method in class net.co.java.entity.
Player.Inventory
CPWorth
- Variable in class net.co.java.item.
ItemPrototype
createAuthorizationPromise(String)
- Method in class net.co.java.model.
Mock
createAuthorizationPromise(String)
- Method in interface net.co.java.model.
Model
Create an AuthorizationPromise
createAuthorizationPromise(String)
- Method in class net.co.java.model.
PostgreSQL
createCharacter(Character_Creation_Packet)
- Method in class net.co.java.model.
Mock
createCharacter(Character_Creation_Packet)
- Method in interface net.co.java.model.
Model
Add a new character in the model
createCharacter(Character_Creation_Packet)
- Method in class net.co.java.model.
PostgreSQL
createPlayerIdentity()
- Method in class net.co.java.model.
AbstractModel
Cryptographer
- Class in
net.co.java.cipher
Cryptographer()
- Constructor for class net.co.java.cipher.
Cryptographer
A
B
C
D
E
F
G
H
I
J
L
M
N
O
P
R
S
T
U
V
W
X
Y
Overview
Package
Class
Use
Tree
Deprecated
Index
Help
Prev Letter
Next Letter
Frames
No Frames
All Classes


| Supplemental
Table 8: Enrichment of GeneOntology classifications at 120hpf for
2DLCMSMS and 2D-PAGE identification |
|
|
| |
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
| 120
hpf 2D-LCMSMS GeneOntology enrichment - Biological Process |
|
|
|
| term |
count |
total |
p |
description |
condensed Term |
Description |
|
| GO:0009084 |
3 |
19 |
0.007 |
glutamine family amino acid biosynthesis |
GO:0044237 |
cellular metabolism |
|
| GO:0018149 |
3 |
19 |
0.007 |
peptide cross-linking |
GO:0044237 |
cellular metabolism |
|
| GO:0006526 |
2 |
7 |
0.009 |
arginine biosynthesis |
GO:0044237 |
cellular metabolism |
|
| GO:0006510 |
2 |
7 |
0.009 |
ATP-dependent proteolysis |
GO:0044237 |
cellular metabolism |
|
| GO:0008652 |
5 |
68 |
0.015 |
amino acid biosynthesis |
GO:0044237 |
cellular metabolism |
|
| GO:0008632 |
1 |
1 |
0.021 |
apoptotic program |
GO:0008219 |
cell death |
|
| GO:0006919 |
1 |
1 |
0.021 |
caspase activation |
GO:0008219 |
cell death |
|
| GO:0043280 |
1 |
1 |
0.021 |
positive regulation of caspase activity |
GO:0008219 |
cell death |
|
| GO:0043026 |
1 |
1 |
0.021 |
regulation of caspase activation |
GO:0008219 |
cell death |
|
| GO:0043281 |
1 |
1 |
0.021 |
regulation of caspase activity |
GO:0008219 |
cell death |
|
| GO:0006481 |
1 |
1 |
0.021 |
C-terminal protein amino acid methylation |
GO:0044237 |
cellular metabolism |
|
| GO:0018410 |
1 |
1 |
0.021 |
peptide or protein carboxyl-terminal blocking |
GO:0044237 |
cellular metabolism |
|
| GO:0000719 |
1 |
1 |
0.021 |
photoreactive repair |
GO:0044237 |
cellular metabolism |
|
| GO:0006290 |
1 |
1 |
0.021 |
pyrimidine dimer repair |
GO:0044237 |
cellular metabolism |
|
| GO:0045926 |
1 |
1 |
0.021 |
negative regulation of growth |
GO:0040007 |
growth |
|
| GO:0045967 |
1 |
1 |
0.021 |
negative regulation of growth rate |
GO:0040007 |
growth |
|
| GO:0040009 |
1 |
1 |
0.021 |
regulation of growth rate |
GO:0040007 |
growth |
|
| GO:0051345 |
1 |
1 |
0.021 |
positive regulation of hydrolase activity |
GO:0048518 |
positive regulation of biological process |
|
| GO:0007275 |
29 |
924 |
0.025 |
development |
GO:0007275 |
development |
|
| GO:0006525 |
2 |
12 |
0.026 |
arginine metabolism |
GO:0044237 |
cellular metabolism |
|
| GO:0000051 |
2 |
12 |
0.026 |
urea cycle intermediate metabolism |
GO:0044237 |
cellular metabolism |
|
| GO:0051169 |
3 |
31 |
0.028 |
nuclear transport |
GO:0006810 |
transport |
|
| GO:0016477 |
3 |
34 |
0.035 |
cell migration |
GO:0006928 |
cell motility |
|
| GO:0009953 |
2 |
14 |
0.035 |
dorsal/ventral pattern formation |
GO:0007275 |
development |
|
| GO:0009309 |
5 |
86 |
0.037 |
amine biosynthesis |
GO:0044237 |
cellular metabolism |
|
| GO:0044271 |
5 |
86 |
0.037 |
nitrogen compound biosynthesis |
GO:0044237 |
cellular metabolism |
|
| GO:0006352 |
3 |
35 |
0.038 |
transcription initiation |
|
transcription initiation |
|
| GO:0006913 |
3 |
36 |
0.041 |
nucleocytoplasmic transport |
GO:0016043 |
cell organization and biogenesis |
|
| GO:0008354 |
1 |
2 |
0.042 |
germ cell migration |
GO:0006928 |
cell motility |
|
| GO:0006370 |
1 |
2 |
0.042 |
mRNA capping |
GO:0044237 |
cellular metabolism |
|
| GO:0009452 |
1 |
2 |
0.042 |
RNA capping |
GO:0044237 |
cellular metabolism |
|
| GO:0007179 |
1 |
2 |
0.042 |
transforming growth factor beta receptor signaling pathway |
GO:0007165 |
signal transduction |
|
| GO:0040007 |
5 |
92 |
0.047 |
growth |
GO:0040007 |
growth |
|
| |
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
| 120
hpf 2D-LCMSMS GeneOntology enrichment - Molecular Function |
|
|
|
| term |
count |
total |
p |
description |
condensed Term |
description |
|
| GO:0004143 |
3 |
18 |
0.005 |
diacylglycerol kinase activity |
GO:0003824 |
catalytic activity |
|
| GO:0004994 |
2 |
11 |
0.018 |
somatostatin receptor activity |
GO:0005488 |
binding |
|
| GO:0003842 |
1 |
1 |
0.019 |
1-pyrroline-5-carboxylate dehydrogenase activity |
GO:0003824 |
catalytic activity |
|
| GO:0004327 |
1 |
1 |
0.019 |
formaldehyde dehydrogenase (glutathione) activity |
GO:0003824 |
catalytic activity |
|
| GO:0004715 |
1 |
1 |
0.019 |
non-membrane spanning protein tyrosine kinase activity |
GO:0003824 |
catalytic activity |
|
| GO:0004738 |
1 |
1 |
0.019 |
pyruvate dehydrogenase activity |
GO:0003824 |
catalytic activity |
|
| GO:0004745 |
1 |
1 |
0.019 |
retinol dehydrogenase activity |
GO:0003824 |
catalytic activity |
|
| GO:0004801 |
1 |
1 |
0.019 |
transaldolase activity |
GO:0003824 |
catalytic activity |
|
| GO:0008460 |
1 |
1 |
0.019 |
dTDP-glucose 4,6-dehydratase activity |
GO:0003824 |
catalytic activity |
|
| GO:0008188 |
4 |
54 |
0.020 |
neuropeptide receptor activity |
GO:0005488 |
binding |
|
| GO:0042923 |
4 |
54 |
0.020 |
neuropeptide binding |
GO:0005488 |
binding |
|
| GO:0030594 |
7 |
148 |
0.025 |
neurotransmitter receptor activity |
GO:0005488 |
binding |
|
| GO:0042165 |
7 |
148 |
0.025 |
neurotransmitter binding |
GO:0005488 |
binding |
|
| GO:0016645 |
2 |
13 |
0.025 |
oxidoreductase activity, acting on the CH-NH group of donors |
GO:0003824 |
catalytic activity |
|
| GO:0016712 |
3 |
34 |
0.027 |
oxidoreductase activity |
GO:0003824 |
catalytic activity |
|
| GO:0004497 |
7 |
155 |
0.030 |
monooxygenase activity |
GO:0003824 |
catalytic activity |
|
| GO:0004674 |
25 |
888 |
0.038 |
2 protein serine/threonine kinase activity |
GO:0003824 |
catalytic activity |
|
| GO:0030599 |
1 |
2 |
0.038 |
pectinesterase activity |
GO:0003824 |
catalytic activity |
|
| GO:0005381 |
1 |
2 |
0.038 |
iron ion transporter activity |
GO:0005215 |
transporter activity |
|
| |
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
| 120
hpf 2D-LCMSMS GeneOntology enrichment - Cellular Process |
|
|
|
| term |
count |
total |
p |
description |
condensed Term |
Description |
|
| GO:0005741 |
3 |
15 |
0.004 |
mitochondrial outer membrane |
GO:0005622 |
intracellular |
|
| GO:0019867 |
4 |
34 |
0.007 |
outer membrane |
GO:0005622 |
intracellular |
|
| GO:0005740 |
8 |
142 |
0.015 |
mitochondrial membrane |
GO:0005622 |
intracellular |
|
| GO:0005882 |
3 |
25 |
0.018 |
intermediate filament |
GO:0005622 |
intracellular |
|
| GO:0045111 |
3 |
25 |
0.018 |
intermediate filament cytoskeleton |
GO:0005622 |
intracellular |
|
| GO:0016513 |
1 |
1 |
0.022 |
core-binding factor complex |
GO:0005622 |
intracellular |
|
| GO:0009320 |
1 |
1 |
0.022 |
phosphoribosylaminoimidazole carboxylase complex |
GO:0043234 |
protein complex |
|
| GO:0005739 |
11 |
253 |
0.027 |
5 mitochondrion |
GO:0005622 |
intracellular |
|
| GO:0042612 |
3 |
31 |
0.031 |
MHC class I protein complex |
GO:0043234 |
protein complex |
|
| GO:0001772 |
3 |
32 |
0.034 |
immunological synapse |
GO:0016020 |
membrane |
|
| GO:0042611 |
3 |
32 |
0.034 |
MHC protein complex |
GO:0043234 |
protein complex |
|
| GO:0005742 |
1 |
2 |
0.044 |
mitochondrial outer membrane translocase complex |
GO:0005622 |
intracellular |
|
| |
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
| 120
hpf 2D-PAGE GeneOntology enrichment - Biological Process |
|
|
|
| term |
count |
total |
p |
description |
condensed Term |
description |
|
| GO:0000165 |
1 |
1 |
0.003 |
MAPKKK cascade |
GO:0007154 |
cell communication |
|
| GO:0000272 |
1 |
6 |
0.019 |
polysaccharide catabolic process |
GO:0000272 |
metabolic process |
|
| GO:0001570 |
1 |
2 |
0.006 |
vasculogenesis |
GO:0048869 |
cellular developmental process |
|
| GO:0006030 |
1 |
7 |
0.022 |
chitin metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006032 |
1 |
6 |
0.019 |
chitin catabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006040 |
1 |
10 |
0.032 |
amino sugar metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006041 |
1 |
10 |
0.032 |
glucosamine metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006043 |
1 |
6 |
0.019 |
glucosamine catabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006044 |
1 |
10 |
0.032 |
N-acetylglucosamine metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006046 |
1 |
6 |
0.019 |
N-acetylglucosamine catabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006139 |
20 |
4092 |
0.029 |
nucleobase, nucleoside, nucleotide and nucleic acid metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006323 |
5 |
382 |
0.008 |
DNA packaging |
GO:0044237 |
cellular metabolic process |
|
| GO:0006325 |
5 |
382 |
0.008 |
establishment and/or maintenance of chromatin architecture |
GO:0016043 |
cellular component organization and biogenesis |
|
| GO:0006333 |
5 |
342 |
0.005 |
chromatin assembly or disassembly |
GO:0016043 |
cellular component organization and biogenesis |
|
| GO:0006350 |
11 |
1874 |
0.035 |
transcription |
GO:0044237 |
cellular metabolic process |
|
| GO:0006464 |
14 |
2614 |
0.036 |
protein modification |
GO:0044237 |
cellular metabolic process |
|
| GO:0006486 |
2 |
101 |
0.042 |
protein amino acid glycosylation |
GO:0044237 |
cellular metabolic process |
|
| GO:0006497 |
1 |
12 |
0.038 |
protein amino acid lipidation |
GO:0044237 |
cellular metabolic process |
|
| GO:0006505 |
1 |
5 |
0.016 |
GPI anchor metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006506 |
1 |
5 |
0.016 |
GPI anchor biosynthetic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006643 |
2 |
81 |
0.028 |
membrane lipid metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006644 |
2 |
70 |
0.021 |
phospholipid metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006650 |
2 |
25 |
0.003 |
glycerophospholipid metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006793 |
12 |
2015 |
0.025 |
phosphorous metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006796 |
12 |
2015 |
0.025 |
phosphate metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0006888 |
2 |
29 |
0.004 |
ER to Golgi vesicle-mediated transport |
GO:0016043 |
cellular component organization and biogenesis |
|
| GO:0006936 |
1 |
2 |
0.006 |
muscle contraction |
GO:0006936 |
muscle contraction |
|
| GO:0007001 |
5 |
446 |
0.014 |
chromosome organization and biogenesis (sensu Eukaryota) |
GO:0016043 |
cellular component organization and biogenesis |
|
| GO:0007243 |
1 |
7 |
0.022 |
protein kinase cascade |
GO:0007154 |
cell communication |
|
| GO:0007254 |
1 |
1 |
0.003 |
JNK cascade |
GO:0007154 |
cell communication |
|
| GO:0008152 |
50 |
11149 |
0.000 |
metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0009101 |
2 |
101 |
0.042 |
glycoprotein biosynthetic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0016052 |
2 |
85 |
0.030 |
carbohydrate catabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0030384 |
2 |
20 |
0.002 |
phosphoinositide metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0031098 |
1 |
1 |
0.003 |
stress activaterd protein kinase signalling pathway |
GO:0007154 |
cell communication |
|
| GO:0042158 |
1 |
12 |
0.038 |
lipoprotein biosynthetic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0043170 |
38 |
8105 |
0.002 |
macromolecule metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0043283 |
30 |
6144 |
0.005 |
biopolymer metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0043412 |
14 |
2661 |
0.041 |
biopolymer modification |
GO:0044237 |
cellular metabolic process |
|
| GO:0043413 |
2 |
101 |
0.042 |
biopolymer glycosylation |
GO:0044237 |
cellular metabolic process |
|
| GO:0043473 |
1 |
2 |
0.006 |
pigmentation |
GO:0043473 |
pigmentation |
|
| GO:0044237 |
47 |
9787 |
0.000 |
cellular metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0044238 |
46 |
9409 |
0.000 |
primary metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0044247 |
1 |
6 |
0.019 |
cellular polysaccharide catabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0044260 |
21 |
4325 |
0.027 |
cellular macromolecule metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0044267 |
20 |
4282 |
0.044 |
cellular protein metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0044275 |
2 |
85 |
0.030 |
cellular carbohydrate metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0045045 |
2 |
105 |
0.045 |
secretory pathway |
GO:0044237 |
cellular metabolic process |
|
| GO:0046348 |
1 |
6 |
0.019 |
amino sugar catabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0046474 |
1 |
10 |
0.032 |
glycerophospholipid biosynthetic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0046488 |
1 |
15 |
0.047 |
phosphatidylinositol metabolic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0046489 |
1 |
5 |
0.016 |
phosphoinositide biosynthetic process |
GO:0044237 |
cellular metabolic process |
|
| GO:0046903 |
2 |
109 |
0.048 |
secretion |
GO:0051234 |
establishment of localization |
|
| GO:0048193 |
2 |
30 |
0.004 |
Golgi vesicle transport |
GO:0016043 |
cellular component organization and biogenesis |
|
| GO:0051276 |
5 |
451 |
0.015 |
chromosome organization and biogenesis |
GO:0016043 |
cellular component organization and biogenesis |
|
| |
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
| 120
hpf 2D-PAGE GeneOntology enrichment - Molecular Function |
|
|
|
| term |
count |
total |
p |
description |
condensed Term |
description |
|
| GO:0005386 |
7 |
406 |
0.002 |
carrier activity |
GO:0005215 |
transporter activity |
|
| GO:0017111 |
9 |
733 |
0.004 |
nucleoside-triphosphatase activity |
GO:0003824 |
catalytic activity |
|
| GO:0005385 |
1 |
1 |
0.004 |
zinc ion transporter activity |
GO:0005215 |
transporter activity |
|
| GO:0017095 |
1 |
1 |
0.004 |
heparan sulfate 6-O-sulfotransferase activity |
GO:0003824 |
catalytic activity |
|
| GO:0016462 |
9 |
744 |
0.005 |
pyrophosphatase activity |
GO:0003824 |
catalytic activity |
|
| GO:0016818 |
9 |
754 |
0.005 |
hydrolase activity, acting on acid anhydrides, in
phosphorus-containing anhydrides |
GO:0003824 |
catalytic activity |
|
| GO:0016817 |
9 |
790 |
0.007 |
hydrolase activity, acting on acid anhydrides |
GO:0003824 |
catalytic activity |
|
| GO:0005351 |
2 |
32 |
0.008 |
sugar porter activity |
GO:0005215 |
transporter activity |
|
| GO:0001565 |
1 |
2 |
0.009 |
phorbol ester receptor activity |
GO:0004871 |
signal transducer activity |
|
| GO:0004697 |
1 |
2 |
0.009 |
protein kinase C activity |
GO:0003824 |
catalytic activity |
|
| GO:0004700 |
1 |
2 |
0.009 |
atypical protein kinase C activity |
GO:0003824 |
catalytic activity |
|
| GO:0042625 |
4 |
190 |
0.009 |
ATPase activity, coupled to transmembrane movement of ions |
GO:0003824 |
catalytic activity |
|
| GO:0042626 |
5 |
297 |
0.009 |
ATPase activity, coupled to transmembrane movement of substances |
GO:0003824 |
catalytic activity |
|
| GO:0043492 |
5 |
297 |
0.009 |
ATPase activity, coupled to movement of substances |
GO:0003824 |
catalytic activity |
|
| GO:0015399 |
4 |
195 |
0.010 |
primary active transporter activity |
GO:0005215 |
transporter activity |
|
| GO:0015405 |
4 |
195 |
0.010 |
P-P-bond-hydrolysis-driven transporter activity |
GO:0005215 |
transporter activity |
|
| GO:0051119 |
2 |
39 |
0.012 |
sugar transporter activity |
GO:0005215 |
transporter activity |
|
| GO:0016820 |
5 |
333 |
0.014 |
hydrolase activity, acting on acid anhydrides, catalyzing
transmembrane movement of substances |
GO:0003824 |
catalytic activity |
|
| GO:0015662 |
3 |
119 |
0.014 |
ATPase activity, coupled to transmembrane movement of ions, phosphorylative mechanism |
GO:0003824 |
catalytic activity |
|
| GO:0015144 |
2 |
44 |
0.015 |
carbohydrate transporter activity |
GO:0005215 |
transporter activity |
|
| GO:0004332 |
1 |
6 |
0.025 |
fructose-bisphosphate aldolase activity |
GO:0003824 |
catalytic activity |
|
| GO:0016832 |
1 |
7 |
0.029 |
aldehyde-lyase activity |
GO:0003824 |
catalytic activity |
|
| GO:0016986 |
1 |
7 |
0.029 |
transcription initiation factor activity |
GO:0030528 |
transcription regulator activity |
|
| GO:0042623 |
5 |
404 |
0.030 |
ATPase activity, coupled |
GO:0003824 |
catalytic activity |
|
| GO:0004303 |
1 |
8 |
0.034 |
estradiol 17-beta-dehydrogenase activity |
GO:0003824 |
catalytic activity |
|
| GO:0004999 |
1 |
8 |
0.034 |
vasoactive intestinal polypeptide receptor activity |
GO:0004871 |
signal transducer activity |
|
| GO:0046915 |
1 |
10 |
0.042 |
transition metal ion transporter activity |
GO:0005215 |
transporter activity |
|
| GO:0015290 |
3 |
192 |
0.049 |
electrochemical potential-driven transporter activity |
GO:0005215 |
transporter activity |
|
| GO:0015291 |
3 |
192 |
0.049 |
porter activity |
GO:0005215 |
transporter activity |
|
| GO:0016229 |
1 |
12 |
0.050 |
steroid dehydrogenase activity |
GO:0003824 |
catalytic activity |
|
| |
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
| 120
hpf 2D-PAGEGeneOntology enrichment Cellular Process |
|
|
|
| term |
count |
total |
p |
description |
condensed Term |
description |
|
| GO:0005622 |
50 |
8500 |
0.000 |
intracellular |
|
|
|
| GO:0005739 |
5 |
194 |
0.001 |
mitochondrion |
|
|
|
| GO:0044444 |
12 |
1070 |
0.001 |
cytoplasm |
|
|
|
| GO:0005737 |
15 |
1615 |
0.002 |
cytoplasm |
|
|
|
| GO:0044424 |
35 |
5557 |
0.002 |
intracellular |
|
|
|
| GO:0031967 |
4 |
138 |
0.003 |
organelle envelope |
|
|
|
| GO:0031975 |
4 |
153 |
0.004 |
envelope |
|
|
|
| GO:0043231 |
24 |
3387 |
0.004 |
intracellular membrane-bound organelle |
|
|
|
| GO:0043227 |
24 |
3390 |
0.004 |
membrane-bound organelle |
|
|
|
| GO:0030141 |
1 |
2 |
0.008 |
secretory granule |
|
|
|
| GO:0005643 |
2 |
33 |
0.008 |
nuclear pore |
|
|
|
| GO:0046930 |
2 |
33 |
0.008 |
pore complex |
|
|
|
| GO:0031965 |
2 |
34 |
0.009 |
nuclear membrane |
|
|
|
| GO:0044453 |
2 |
34 |
0.009 |
nuclear membrane part |
|
|
|
| GO:0043229 |
29 |
4672 |
0.010 |
intracellular organelle |
|
|
|
| GO:0043226 |
29 |
4673 |
0.010 |
organelle |
|
|
|
| GO:0005829 |
3 |
112 |
0.011 |
cytosol |
|
|
|
| GO:0044429 |
3 |
113 |
0.012 |
mitochondrial part |
|
|
|
| GO:0005635 |
2 |
41 |
0.013 |
nuclear envelope |
|
|
|
| GO:0000313 |
1 |
7 |
0.029 |
organellar ribosome |
|
|
|
| GO:0005761 |
1 |
7 |
0.029 |
mitochondrial ribosome |
|
|
|
| GO:0031090 |
4 |
279 |
0.029 |
organelle membrane |
|
|
|
| GO:0005743 |
2 |
66 |
0.031 |
mitochondrial inner membrane |
|
|
|
| GO:0044428 |
3 |
164 |
0.031 |
nuclear part |
|
|
|
| GO:0005681 |
1 |
8 |
0.033 |
spliceosome |
|
|
|
| GO:0019866 |
2 |
70 |
0.035 |
organelle inner membrane |
|
|
|
| GO:0031966 |
2 |
81 |
0.045 |
mitochondrial membrane |
|
|
|
| |
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|