Hugging Face's logo
AbstractPhila's picture
13 2 14

AbstractPhila PRO

AbstractPhil
Kutches's profile picture alexis654's profile picture FiditeNemini's profile picture
·
https://civitai.com/user/AbstractPhila

AI & ML interests

datasets, research papers, experimentation, vision, classification, text encoders, tokenization, llms, diffusion, distillation, and more.

Recent Activity

updated a dataset less than a minute ago
AbstractPhil/datasets-code-test
published a dataset less than a minute ago
AbstractPhil/datasets-code-test
posted an update 1 day ago
Happy Holidays all! geofractal architectural expansions; timm is now a core component for experimenting. As it stands, the system is growing rapidly in one direction, and timm brings a whole lot to the table in another rapid-prototyping direction. Therefore, timm is now a core component for ease-of-use. BaseUtil is a new core component; aka src.geofractal.router.base_util inherits BaseComponent's behavior, so it should allow device movement for util operations which will direct utilization for device-to-device behavior for the upcoming accelerate integration. I'm trying to mitigate the base component structure as much as possible, but the need to chain components in specific orders presented a unique problem. By compartmentalizing utils into structures that can be delegated and moved, these structures can be repurposed, expanded autonomously, reduced autonomously, and more. ChainComponent inherits a subsystem specifically designed to organize multi-system multi-device formulas designated for inception and synchronization purposes. This is meant to allow distributed tasking to multiple-devices in chained utilization. This also enables ease-of-integration into nn.ModuleList with a few other caveats that will be ironed out meant to target wide-distributed models. FusionComponent is specifically dedicated to the new fusion processing system meant for experimental expansion. This includes sub-module schedule control, Component and Tower functional control, device-movement, and will be packaged under the term "gfu.UtilType" as a standard naming convention. "gfc.ComponentTypeName" "gfr.RouterTypeName" "gfu.UtilityTypeName" "gft.TowerTypeName" All of which are basically just import thing as. "gf.AnythingTopLevelPackaged" which will include the core. Better debugging for compilation I'm in prototyping phases of a better debugging for compiled wide models and will prepare a baseline component readout structure by the end of the day today or tomorrow.
View all activity

Organizations

DeepGHS's profile picture BangumiBase's profile picture Abstract Powered Research's profile picture