You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- ✅ Optimized for device stability and thermal performance
54
+
- ✅ Fully supported by all downstream tools
55
+
- ✅ Guaranteed to work reliably
56
+
- ✅ Recommended for production use and research studies
57
+
58
+
**Recommended for:**
59
+
- Production deployments
60
+
- Large-scale data collection
61
+
- Research studies requiring reliable data
62
+
- Users who want maximum compatibility
63
+
- First-time Aria users
64
+
65
+
### When to Consider Custom Profiles
66
+
67
+
**Custom profiles** may be appropriate for:
68
+
- Advanced research with specific sensor requirements
69
+
- Prototyping new applications
70
+
- Experimental configurations
71
+
- Specialized use cases not covered by pre-defined profiles
72
+
73
+
**⚠️ Important:** Custom profiles should only be used by advanced users who understand the risks and limitations.
74
+
75
+
---
76
+
77
+
## Custom Profiles {#custom_profile_example}
78
+
79
+
### Overview
80
+
81
+
Custom profiles allow advanced users to define their own sensor configurations for specialized research needs. However, **custom profiles come with significant risks and limitations** and should be used with caution.
82
+
83
+
### ⚠️ Important Considerations and Risks
84
+
85
+
Before creating a custom profile, understand these critical limitations:
86
+
87
+
#### 1. Device Stability and Data Quality
88
+
89
+
**Thermal and Power Issues:**
90
+
- Custom profiles that push sensor settings (e.g., high frame rates, high resolutions, enabling many sensors simultaneously) can cause the device to **overheat** or **drain the battery rapidly**
91
+
- This can lead to **unexpected shutdowns** or **reduced recording/streaming times**
92
+
- Some combinations may trigger warnings in the Aria Companion App, but **not all edge cases are covered automatically**
93
+
- Using extreme values or not basing your custom profile on a tested template **significantly increases these risks**
94
+
95
+
**Data Quality Risks:**
96
+
- Unusual sensor configurations may result in:
97
+
- Poor data quality
98
+
- Synchronization issues between sensors
99
+
- Missing data streams
100
+
- Inconsistent sensor performance
101
+
-**These issues may not be immediately apparent** and could compromise your research data
102
+
103
+
**Fragmented Datasets:**
104
+
- Custom profiles can lead to fragmented datasets, making it harder to:
105
+
- Compare data across different studies
106
+
- Aggregate data from multiple users
107
+
- Reproduce research results
108
+
- This **reduces the overall utility** of the data for broader research purposes
109
+
110
+
#### 2. Compatibility and Downstream Tooling
111
+
112
+
**Tooling Incompatibility:**
113
+
- Downstream tools (e.g., Project Aria Tools, MPS, analytics pipelines) **may not be fully compatible** with all custom profile configurations
114
+
- Data recorded with custom profiles may:
115
+
- Not be processed correctly by standard tools
116
+
- Require additional engineering work to support new formats
117
+
- Be incompatible with existing analysis pipelines
118
+
119
+
**Lack of Standardization:**
120
+
- Custom profiles are **not as thoroughly tested or supported** as pre-defined profiles
121
+
- This can lead to:
122
+
- Unexpected issues when using standard tools
123
+
- Difficulties sharing data with collaborators
124
+
- Limited community support
125
+
126
+
#### 3. Known Bugs and Open Issues
127
+
128
+
**Sensor Data Retrieval:**
129
+
- There have been reports of **issues retrieving certain sensor data** (e.g., GPS) when using custom profiles
130
+
- These issues may not be present with recommended pre-defined profiles
131
+
132
+
**Parameter Guardrails:**
133
+
- While the Companion App includes some guardrails, **not all problematic combinations are blocked**
134
+
- Users may still encounter hardware or data quality issues when defining profiles via the SDK
135
+
136
+
**⚠️ Use at Your Own Risk:**
137
+
Custom profiles are provided as-is for advanced users. Meta does not guarantee stability, data quality, or tool compatibility for custom profile configurations.
138
+
139
+
---
140
+
141
+
### Custom Profile Template
142
+
143
+
Below is a template for creating custom profiles. **It is strongly recommended** to base your custom profile on one of the pre-defined profiles (e.g., profile8) rather than starting from scratch.
144
+
145
+
This example is based on **profile8** with the following modifications:
146
+
-**RGB frame rate**: Reduced from 10Hz to 5Hz
147
+
-**SLAM camera frame rate**: Reduced from 30Hz to 10Hz
148
+
-**Hand tracking**: Reduced from 30Hz to 10Hz
49
149
50
150
```json
51
151
{
@@ -146,3 +246,90 @@ Here is an example of custom profile. This profile is a modified based on profil
146
246
]
147
247
}
148
248
```
249
+
250
+
### Template Notes
251
+
252
+
This example demonstrates a **conservative approach** to customization: making minimal changes to a tested profile (profile8) to reduce power consumption while maintaining core functionality.
253
+
254
+
---
255
+
256
+
## Best Practices for Custom Profiles
257
+
258
+
If you must use a custom profile, follow these guidelines:
259
+
260
+
### 1. Start from a Pre-defined Profile
261
+
- ✅ Base your custom profile on profile8, profile9, or profile10
262
+
- ✅ Make incremental changes rather than dramatic modifications
263
+
- ❌ Avoid starting with a blank profile or extreme parameter values
264
+
265
+
### 2. Test Thoroughly
266
+
- Test the profile with short recordings first
267
+
- Monitor device temperature during use
268
+
- Check battery consumption rates
269
+
- Verify all expected sensor streams are present
270
+
- Validate data quality before large-scale data collection
271
+
272
+
### 3. Monitor Device Health
273
+
- Watch for thermal warnings in the Companion App
274
+
- Note any unexpected shutdowns or errors
275
+
- Track recording duration vs. battery life
276
+
- Monitor data completeness and quality
277
+
278
+
### 4. Conservative Parameter Selection
279
+
-**Frame rates**: Lower rates reduce power and thermal load
280
+
-**Resolution**: Higher resolutions increase data size and processing
![meta-codesync[bot]](https://avatars.githubusercontent.com/in/1373969?v=4&size=40){kind=avatar}
0 commit comments