Resource inventory¶
Find a route for College of Information Science research or teaching. Filter by resource type and location, then open an entry for access, cost, limitations and dated sources.
Download inventory CSV · Develop a resource request · Detailed platform references
32 entries
UITS Support
Campus technology help: NetID, software and service troubleshooting, with routing to specialist teams.
Contact: UITS 24/7 Support Center · 520-626-8324 · service.arizona.edu
Access, costs, limitations and sources
Access: University faculty, staff and students can contact the UITS 24/7 Support Center by phone, chat or online ticket.
Cost: Basic diagnostics and fixes are available at no cost to campus community members. Repair services and specialist resources may have separate terms; confirm before use.
Limits: General support does not guarantee RSE time, research workflow development, hardware capacity or an allocation. Repair and specialist service terms need confirmation.
Support: Campus applications, accounts, connectivity, software installation and basic device troubleshooting; specialist needs are routed for confirmation.
Funding: University support service; specialist capacity and separate charges require confirmation.
Review basis: 2026-10-20
Support channels and no-cost basic diagnostics verified on the UITS support page October 20, 2026. College-specific service ownership corrected at Greg Chism’s request.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
College hardware, labs and loan equipment
Identify local equipment, lab access and any loan pool; capacity is not yet inventoried.
Contact: Barney Maccabe or Greg Chism — working-group point people
Access, costs, limitations and sources
Access: Ask Barney Maccabe or Greg Chism to coordinate a roster of machines, locations, owners, access rules and any loan pool.
Cost: Unknown; inventory existing commitments and hours before proposing funding.
Limits: No shared college CPU/GPU pool, equipment checkout entitlement or spare capacity is verified.
Support: Barney Maccabe or Greg Chism — working-group point people
Funding: To document; no new funding, staff time or loan inventory assumed.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Inventory question, not a verified service entitlement. Routing contact designated by the user; profile confirms role/email.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
College software, datasets and agreements
Clarify local software, datasets, agreements and renewal ownership.
Contact: Barney Maccabe or Greg Chism — working-group point people
Access, costs, limitations and sources
Access: Ask the working group to identify license/data owners, storage, renewals and permitted research/classroom use.
Cost: Unknown; inventory existing commitments and hours before proposing funding.
Limits: No college license roster, API allowance or training/distribution rights verified.
Support: Barney Maccabe or Greg Chism — working-group point people
Funding: To document; no new funding, staff time or loan inventory assumed.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Inventory question, not a verified service entitlement. Routing contact designated by the user; profile confirms role/email.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
College research labs and collaborators
Find research capabilities and possible collaborators; shared access requires agreement.
Contact: College research-labs directory; Barney Maccabe or Greg Chism for working-group coordination
Access, costs, limitations and sources
Access: Explore the college research-labs directory; approach the relevant lab lead for a research collaboration.
Cost: No general-use fee schedule or guaranteed shared access published.
Limits: A lab listing establishes research capability, not open compute, staff availability or a classroom reservation.
Support: College research-labs directory; Barney Maccabe or Greg Chism for working-group coordination
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
co/lab: Critical Archives & Curation Collaborative
Explore critical archives, curation and community-centered data work.
Contact: Co-directors Jamie A. Lee and Zack Lischer-Katz — lab page
Access, costs, limitations and sources
Access: Discuss digital curation, obsolete media/computers and digital-forensics collaborations with the co-directors.
Cost: Shared equipment access, project charges and supervision not published.
Limits: Research collaboration and preservation capability; no public equipment checkout policy, GPU entitlement or staffed digitization service.
Support: Co-directors Jamie A. Lee and Zack Lischer-Katz — lab page
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
XRG: Extended Reality & Games Lab
Explore extended reality and games capabilities; access and equipment availability need confirmation.
Contact: Lila Boz and Ren Boz — lab leads listed on XRG page
Access, costs, limitations and sources
Access: Discuss XR, virtual/augmented reality and interaction research with the lab leads.
Cost: No general-use equipment rate or access entitlement published.
Limits: Research lab, not a documented open GPU lab or college equipment-loan service; confirm scheduling and participation.
Support: Lila Boz and Ren Boz — lab leads listed on XRG page
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
College course technology requirements
Check course software and device requirements before selecting a platform.
Contact: Course lead or faculty adviser; college office for routing
Access, costs, limitations and sources
Access: Check the program-specific minimum hardware and operating-system requirements before designing an activity.
Cost: Student-owned device requirements; no provided machine or subsidy established.
Limits: Requirements vary by degree. Device specifications do not establish college-owned inventory or access to loan equipment.
Support: Course lead or faculty adviser; college office for routing
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
Campus HPC: Puma CPU and GPU
Shared Puma CPU/GPU allocation for PI groups; class groups are permitted, with queue and support limits.
Contact: HPC Consult — ServiceNow ticket
Access, costs, limitations and sources
Access: Registered faculty PI groups receive 150,000 CPU core-hours per PI group each month, shared by research and class groups. CPU, GPU and high-memory jobs debit the same CPU-based pool; this is not 150,000 GPU-hours. Unused hours expire at month end.
Cost: Standard allocation and HPC consulting have no charge. High-priority access requires a separate buy-in; windfall jobs are lower-priority and preemptible.
Limits: Published standard concurrency ceiling: four GPUs and 3,290 CPUs per group, shared across users; this is a limit, not a reservation. Shared queues give no guaranteed start time or priority for assignment deadlines. Instructors provide student support; HPC Consult helps instructors on weekdays, not weekends or university holidays. Confirm remaining PI balance, resource limits and course fit; no class reservation is established. Lynx/H200 is explicitly not available yet. Published Puma MIG memory figures differ between the table and narrative; confirm the requested device.
Support: HPC Consult via ServiceNow; published hours 8 am-5 pm Monday-Friday, excluding university holidays.
Funding: University standard allocation; buy-in and special-project awards have separate conditions. Local support capacity is not implied.
Source 1 ↗ · Source 2 ↗ · Source 3 ↗ · Source 4 ↗ · Source 5 ↗
Review basis: 2026-10-20 — current public allocation, teaching, hardware and support documentation; no signed-in balance or workload test
Current published Puma allocation and classroom permission verified directly. This does not verify Greg’s remaining balance, a course reservation, allocation renewal or staffing. A Jeremy Frumkin (UITS) slide in supplied October 14–15 briefing notes adds hardware context, not a classroom allocation or reservation; the slide lists 40 GB A100 MIG slices on Puma.
Next: Check the actual remaining PI balance with va; identify CPU/GPU shape and concurrency limits, then test the workflow and arrange instructor-led support. Check job-limits <group_name> for live group usage/limits; Open OnDemand has additional per-job limits.
Campus HPC: Puma classroom computing
Puma is available for classes; the PI allocation is shared and immediate CPU/GPU access is not guaranteed.
Contact: HPC Consult — instructor should open a ticket
Access, costs, limitations and sources
Access: Faculty PIs may create class groups for instruction on Puma. 150,000 CPU core-hours per PI group each month, shared by research and class groups. CPU, GPU and high-memory jobs debit the same CPU-based pool; this is not 150,000 GPU-hours. Unused hours expire at month end.
Cost: No added class allocation or dedicated class storage. Standard allocation and consulting have no charge; research and teaching share the PI pool.
Limits: Published standard concurrency ceiling: four GPUs and 3,290 CPUs per group, shared across users; this is a limit, not a reservation. Shared queues give no guaranteed start time or priority for assignment deadlines. Instructors provide student support; HPC Consult helps instructors on weekdays, not weekends or university holidays. Confirm remaining PI balance, resource limits and course fit; no class reservation is established.
Support: HPC Consult helps instructors set up class groups and troubleshoot infrastructure. Students get course support from their instructor/team; no individual student consulting is promised.
Funding: Institutional or project service; dedicated college capacity/funding not established.
Source 1 ↗ · Source 2 ↗ · Source 3 ↗ · Source 4 ↗ · Source 5 ↗ · Source 6 ↗
Review basis: 2026-10-20 — current public teaching and allocation policies; no signed-in balance, reservation or class-load test
The current teaching policy explicitly permits Puma class groups, superseding the earlier Ocelote-only uncertainty. Specific course capacity, remaining balance, supported data and readiness still need validation. A Jeremy Frumkin (UITS) slide in supplied October 14–15 briefing notes adds hardware context, not a classroom allocation or reservation; the slide lists 40 GB A100 MIG slices on Puma.
Next: Create the course class group, check remaining PI hours, test representative assignments and peak load, and agree student support, queue-tolerant deadlines and fallback. Check job-limits <group_name> for live group usage/limits; Open OnDemand has additional per-job limits.
HPC active storage and transfers
Active research storage and data transfers; not an independent backup.
Contact: HPC Consult — ServiceNow ticket
Access, costs, limitations and sources
Access: HPC account: 50 GB home; PI group: 500 GB communal space. Temporary xdisk on request: 200 GB–20 TB, up to 300 days.
Cost: Standard spaces supplied with account/group; rental is a separate priced service.
Limits: HPC data are not backed up; xdisk is temporary and node /tmp is cleared after a job. Storage quotas do not provide preservation or regulated-data approval.
Support: HPC Consult — ServiceNow ticket
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
HPC software, containers and shared model data
Find supported HPC software, containers and shared model data.
Contact: HPC Consult — software/setup questions
Access, costs, limitations and sources
Access: Use HPC modules, user environments and containers; shared datasets include Llama 2 and AlphaFold inputs.
Cost: Open-source tools may have no license charge; licensed products and model terms still apply. Compute uses the allocation.
Limits: Availability varies by module/version. Llama 2 has its own community license; model memory/storage requirements can be substantial. A software listing is not permission for every use.
Support: HPC Consult — software/setup questions
Funding: Institutional or project service; dedicated college capacity/funding not established.
Source 1 ↗ · Source 2 ↗ · Source 3 ↗ · Source 4 ↗
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
HPC consulting and visualization support
Consult on HPC workflows and visualization; specialist capacity is not assumed.
Contact: HPC Consult ticket; visualization: vislab-consult@list.arizona.edu
Access, costs, limitations and sources
Access: Open a ServiceNow ticket for onboarding, queue issues, code optimization and resource advice; request visualization help through its team.
Cost: HPC consulting is published as free of cost.
Limits: HPC team support hours: weekdays 8 a.m.–5 p.m., excluding university holidays. Consultation is not an assigned engineer or individualized student homework support.
Support: HPC Consult ticket; visualization: vislab-consult@list.arizona.edu
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
AI Verde → Arizona AI Assistant: planned transition
ORAI reports an Arizona AI Assistant transition and planned Bedrock credit; terms need confirmation.
Contact: Wolfgang Jentner · Office of Responsible AI (ORAI) · wjentner@arizona.edu
Access, costs, limitations and sources
Access: Wolfgang Jentner at the Office of Responsible AI (ORAI), via Greg Chism, reports AI Verde will be sunset in favor of Arizona AI Assistant. Use the new portal to check sign-in, API access and enrollment; migration timing and eligibility need confirmation.
Cost: Planned $200/month of AWS Bedrock credit, reported by Wolfgang Jentner at ORAI and relayed by Greg Chism on October 19, 2026. Confirm who receives the allowance, renewal, covered usage and overage controls; not an unlimited compute or GPU-training allocation.
Limits: Supplied ORAI pricing screenshot lists 12 hosted models and per-token prices. These campus gateway rates differ from direct-provider rates. Credit is not transferred to this site’s OpenAI API; API compatibility, data rules, class concurrency and migration/export still need confirmation.
Support: Wolfgang Jentner · Office of Responsible AI (ORAI) · wjentner@arizona.edu
Funding: Campus Bedrock credit reported by Wolfgang Jentner at ORAI, via Greg Chism; allocation level and renewal terms to confirm.
Source 1 ↗ · Source 2 ↗ · Source 3 ↗ · Source 4 ↗
Review basis: 2026-10-19 — ORAI transition/credit update and pricing screenshot from Wolfgang Jentner, relayed by Greg Chism; portal HTTP 200, no signed-in entitlement test
Public university news describes Arizona AI Assistant as a fall pilot and AI Verde separately. The transition and $200/month credit come from Wolfgang Jentner at ORAI, relayed by Greg Chism; individual entitlements have not been tested. Pricing screenshot received October 19; its capture/effective date is unconfirmed. Confirm live account rates. Primary contact corrected at Greg Chism’s request October 20. ORAI directory confirms the spelling Wolfgang Jentner and wjentner@arizona.edu; primary service responsibility is user-confirmed.
Next: Ask Wolfgang Jentner at ORAI to confirm transition date, account/credit scope, API base URL, permitted data, overage policy and exports.
U of A GenAI
Explore the documented NetID route for campus generative AI tools.
Contact: Responsible AI tools page and campus 24/7 IT support: 520-626-8324
Access, costs, limitations and sources
Access: Active UArizona NetID; published FAQ describes limited early access. Check genai.arizona.edu for availability.
Cost: Published no-cost campus use.
Limits: Models/features may rotate; no guaranteed API, classroom concurrency or GPU-training allocation. Early-access conditions and data-specific exclusions apply; this differs from AI Verde.
Support: Responsible AI tools page and campus 24/7 IT support: 520-626-8324
Funding: Institutional or project service; dedicated college capacity/funding not established.
Source 1 ↗ · Source 2 ↗ · Source 3 ↗
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
Campus software licensing
Check campus software agreements, eligible users and license restrictions.
Contact: UITS 24/7 support — 520-626-8324
Access, costs, limitations and sources
Access: Use the UITS software catalog and student/faculty service routes; check each product and affiliation.
Cost: Student page lists Microsoft 365, Google Apps and Adobe Creative Cloud without added software charge while enrolled; other products are free or discounted. Student services are supported by the IT & Library Fee.
Limits: Eligibility, device counts, renewal and commercial/research use vary. Listed MATLAB/Autodesk etc. do not imply every license or API credit is included.
Support: UITS 24/7 support — 520-626-8324
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
VCAT and Tech Zone software access
Explore remotely available or shared-space software; check application and class fit.
Contact: UITS 24/7 support — 520-626-8324
Access, costs, limitations and sources
Access: VCAT supplies virtual applications through a browser; Tech Zone labs provide installed software. Instructors can request a lab software installation.
Cost: Campus student-service route; fee-supported. Product-specific access and installation charges, if any, must be checked.
Limits: App/version and lab availability vary; not a general-purpose GPU allocation, unrestricted server or always-on research host.
Support: UITS 24/7 support — 520-626-8324
Funding: Institutional or project service; dedicated college capacity/funding not established.
Source 1 ↗ · Source 2 ↗ · Source 3 ↗
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
Libraries Data Cooperative: Python, R and ML support
Seek Python, R, machine-learning and research-data guidance.
Access, costs, limitations and sources
Access: Faculty, staff and students can consult library specialists on data science, visualization, programming and data management.
Cost: No project-specific fee or dedicated engineering allowance established by these pages.
Limits: Consultation, instruction and referrals; no dedicated developer hours, turnaround or ongoing operations commitment.
Support: Sarah Stueve — sarahstueve@arizona.edu (Python/ML); Jeff Oliver — jcoliver@arizona.edu (R/Git/visualization)
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
Digital scholarship and text/data mining
Explore digital scholarship, text analysis and data-mining support.
Contact: Heather Froehlich — froehlich@arizona.edu
Access, costs, limitations and sources
Access: Consult about corpora, text analysis, humanities data, metadata and digital editing; listed open tools include OpenRefine, Voyant, AntConc and CollectionBuilder.
Cost: Listed tools are free to use; sustained project implementation/support not priced here.
Limits: Tool availability does not clear copyright, dataset licensing, hosting, compute or staff time.
Support: Heather Froehlich — froehlich@arizona.edu
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
Library datasets, databases and reuse rights
Check dataset access and reuse rights; library access does not imply redistribution rights.
Contact: Library Collections — LBRY-collectionmanagement@email.arizona.edu
Access, costs, limitations and sources
Access: Use licensed resources under current UA affiliation and the specific agreement. Contact Collections before TDM or use with AI.
Cost: Institutional subscriptions cover authorized access; additional TDM/API rights or fees depend on the agreement.
Limits: Reading access does not authorize bulk download, sharing, training or uploading to public AI tools. Each publisher agreement differs.
Support: Library Collections — LBRY-collectionmanagement@email.arizona.edu
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
GIS software, geospatial data and consultation
Find geospatial software, data and consultation.
Contact: Garrett Smith — garrettsmith@arizona.edu
Access, costs, limitations and sources
Access: Use the Libraries GIS/data guides and repository; discuss ArcGIS, QGIS, R and spatial analysis with a specialist.
Cost: QGIS is open source; ArcGIS eligibility and project-specific data/service terms require checking. No universal paid-product entitlement inferred.
Limits: Data licenses, service quotas and support capacity differ. A geospatial repository is not a general GPU or database-hosting award.
Support: Garrett Smith — garrettsmith@arizona.edu
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
ReDATA: research data and code preservation
Assess research data and code deposits for preservation and reuse.
Contact: ReDATA team — data-management@arizona.edu
Access, costs, limitations and sources
Access: Active faculty/staff, enrolled students and certain DCCs with valid NetID/library privileges can submit eligible final research materials for curatorial review.
Cost: FAQ: no cost to individual UArizona researchers; quota increases depend on need and availability.
Limits: Non-sensitive research materials and rights required; curatorial review mandatory. Not an active database/backup service. Published notice reports intermittent traffic-related errors and automated download restrictions; not a breach.
Support: ReDATA team — data-management@arizona.edu
Funding: Institutional or project service; dedicated college capacity/funding not established.
Source 1 ↗ · Source 2 ↗ · Source 3 ↗
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
Data Science Institute / CyVerse research software expertise
Explore research software expertise; published contact routes need reconfirmation.
Contact: Published DSI contact — RII-datascienceinstitute@arizona.edu (current operation to reconfirm)
Access, costs, limitations and sources
Access: Indexed official DSI pages describe project/proposal consultation and cross-college teams; their live hostnames did not resolve during this review. Reconfirm the current route before relying on it.
Cost: No blanket free engineering-hour entitlement or public project rate established; scope and funding must be agreed.
Limits: Named engineering expertise is not an available appointment or staffed help desk for every course. Confirm capacity, deliverables, maintenance and funding.
Support: DSI — RII-datascienceinstitute@arizona.edu
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — indexed official text retrieved; direct live verification unsuccessful
Official-source search/fetch text supplied the contact and engineering roles, but direct checks of data7.arizona.edu and datascience.arizona.edu failed DNS resolution. This is an availability limitation, not evidence of service closure. No available staff hours verified.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
CCT Data Science: consultation and research software
Explore research data-science consultation and software support.
Contact: CCT Data Science team — current contact/consultation routes
Access, costs, limitations and sources
Access: Drop-in/workshop routes and grant collaboration documented. The 80-hour Data Science Incubator is limited to ALVSCE faculty, staff and students.
Cost: Longer collaboration can use hired effort or a co-PI grant arrangement; Information Science eligibility for other services and rates must be confirmed.
Limits: The ALVSCE incubator is not an 80-hour entitlement for Information Science. Training/drop-in help differs from funded long-term engineering.
Support: CCT Data Science team — current contact/consultation routes
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
CATalyst Studios: XR, making and class partnerships
Explore making, XR and class partnerships; availability needs confirmation.
Contact: CATalyst Studios — contact and consultation booking
Access, costs, limitations and sources
Access: Use Main Library makerspace hours, reserve eligible spaces/VR equipment, or plan a class visit with the team.
Cost: Free workshops are advertised; material/equipment-specific charges and eligibility must be checked.
Limits: Some machines require authorization classes. Reservations, supervision and supplies constrain access; no general-purpose compute/GPU reservation inferred.
Support: CATalyst Studios — contact and consultation booking
Funding: Institutional or project service; dedicated college capacity/funding not established.
Review basis: 2026-10-19 — public documentation; no signed-in entitlement or owner confirmation
Access route, published cost basis and contact checked in public sources. Unpublished quotas, staffing and college capacity remain unknown.
Next: Confirm eligibility, current availability, permitted use and support scope with this contact before relying on the resource.
AI tools and data-use guidance
Check institutional AI-tool and data-use guidance before adoption.
Contact: Responsible AI campus support and current training organizers
Access, costs, limitations and sources
Access: Review the current university decision table before selecting a tool.
Cost: Public guidance; project review effort must be scoped.
Limits: Data categories and account types matter; do not infer authorization from a vendor privacy claim.
Support: University AI, privacy and relevant data owners.
Funding: University guidance; not a compute or staff allocation.
Review basis: 2026-10-19
Published guidance/training route only; not a compute or staff allocation.
Next: Confirm eligibility, available capacity, support commitment and funding with the resource owner.
Campus AI learning and events
Find learning opportunities and training; events do not establish ongoing support.
Contact: Responsible AI campus support and current training organizers
Access, costs, limitations and sources
Access: Follow the university AI resources page for training and event routes.
Cost: Check each offering; staff learning time is still required.
Limits: A course/event is not staffed project support or a reserved technical service.
Support: University AI learning and event organizers.
Funding: University initiative; event availability varies.
Review basis: 2026-10-19
Published guidance/training route only; not a compute or staff allocation.
Next: Confirm eligibility, available capacity, support commitment and funding with the resource owner.
NSF ACCESS
Request project-based CPU and GPU resources; an award and provider fit are required.
Contact: ACCESS support and selected resource provider
Access, costs, limitations and sources
Access: Match the project and teaching/research use to a resource and request.
Cost: Allocated resource access is conditional; operations/support remain separate.
Limits: No award, class reservation or provider benchmark established.
Support: ACCESS support plus the selected resource provider.
Funding: Federally supported allocation route.
Review basis: Earlier compute-ledger review; not newly rechecked
Earlier source-ledger review; current resource-owner access, cost and contact not newly verified in this campus expansion.
Next: Confirm eligibility, available capacity, support commitment and funding with the resource owner.
NAIRR Classroom
Explore eligible instructor-led AI classroom pilots; scope and resources are conditional.
Contact: NAIRR program / current Classroom call
Access, costs, limitations and sources
Access: Check the current instructor/course call and resource terms.
Cost: Conditional award/resource terms; not funding in hand.
Limits: An eligible AI pilot does not supply every course or its ongoing staff support.
Support: Program and resource-specific support.
Funding: Federal pilot opportunity.
Review basis: Earlier compute-ledger review; recheck call before use
Earlier source-ledger review; current resource-owner access, cost and contact not newly verified in this campus expansion.
Next: Confirm eligibility, available capacity, support commitment and funding with the resource owner.
OSPool / throughput computing
Assess opportunistic throughput jobs; this is a different service model from live class notebooks.
Contact: OSPool facilitation / support
Access, costs, limitations and sources
Access: Assess independent, checkpointed research jobs and facilitated onboarding.
Cost: Opportunistic use subject to policy and available capacity.
Limits: Interruptions and queue behavior differ from live classroom sessions.
Support: OSG/OSPool support route.
Funding: Federally supported/shared infrastructure.
Review basis: Earlier compute-ledger review; recheck before use
Earlier source-ledger review; current resource-owner access, cost and contact not newly verified in this campus expansion.
Next: Confirm eligibility, available capacity, support commitment and funding with the resource owner.
MESA / CyVerse collaboration
Explore compatible data-service collaboration; project funding is not a general compute entitlement.
Contact: MESA project team / underlying service provider
Access, costs, limitations and sources
Access: Explore public service and collaboration routes; confirm underlying access.
Cost: Service-specific; no free college compute entitlement inferred.
Limits: Grant participation and advertised products do not establish approved class capacity.
Support: Project/platform maintainers; commitments to confirm.
Funding: IDSS/project and underlying service support differ.
Review basis: Earlier compute-ledger review; recheck before use
Earlier source-ledger review; current resource-owner access, cost and contact not newly verified in this campus expansion.
Next: Confirm eligibility, available capacity, support commitment and funding with the resource owner.
Free GPU and cloud-credit experiments
Use bounded GPU notebooks or credits for preliminary experiments; quotas and hardware vary.
Contact: Provider-specific help routes in comparison
Access, costs, limitations and sources
Access: Compare Kaggle, free Colab and credit-based platforms in the existing directory.
Cost: Quotas, cards and paid conversion vary.
Limits: Useful for bounded experiments; not a guaranteed full-term GPU reservation.
Support: Provider/community support; no class support commitment.
Funding: Provider-sponsored tiers or promotional credits.
Review basis: Earlier compute-ledger review; recheck before use
Earlier source-ledger review; current resource-owner access, cost and contact not newly verified in this campus expansion.
Next: Confirm eligibility, available capacity, support commitment and funding with the resource owner.
Repositories, databases and preservation
Separate code hosting, active databases, scholarly deposits and preservation needs.
Contact: Service-specific contacts in continuity plan
Access, costs, limitations and sources
Access: Match code, active databases, research deposits and archival needs separately.
Cost: Storage, activity and hosting limits vary.
Limits: Compute allocations do not automatically provide durable databases or preservation.
Support: Institutional librarians, data owners and hosting operators.
Funding: Institutional and provider arrangements differ.
Review basis: Earlier compute-ledger review; recheck before use
Earlier source-ledger review; current resource-owner access, cost and contact not newly verified in this campus expansion.
Next: Confirm eligibility, available capacity, support commitment and funding with the resource owner.
Keep the inventory useful¶
Confirm access, owner, support window, funding, costs and limits before changing an entry to verified. Record missing resources as unknown, not unavailable. Use the detailed platform directory for further comparisons.