main
Name already in use
Commits on Feb 15, 2023
-
Flax layers are parametrizable with custom conv_general_dilated.
PiperOrigin-RevId: 509679602
Flax Team committedFeb 15, 2023
Commits on Feb 13, 2023
-
Remove fallbacks for old versions of JAX from Flax.
Flax's setup.py requires JAX >= 0.4.2, so these code paths are dead. PiperOrigin-RevId: 509309356
Commits on Feb 9, 2023
-
Flax layers are parametrizable with custom dot_general.
PiperOrigin-RevId: 508438464
Flax Team committedFeb 9, 2023 -
Replace uses of deprecated JAX sharding APIs with their new names in …
…jax.sharding. This change updates: * {jax.experimental.maps.Mesh, jax.interpreters.pxla.Mesh} to jax.sharding.Mesh * {jax.experimental.PartitionSpec, jax.experimental.pjit.PartitionSpec, jax.interpreters.pxla.PartitionSpec, jax.pxla.PartitionSpec} to jax.sharding.PartitionSpec * jax.experimental.maps.NamedSharding to jax.sharding.NamedSharding. PiperOrigin-RevId: 508404789 -
Merge pull request #2856 from levskaya:point_release4
PiperOrigin-RevId: 508228804
Flax Authors committedFeb 9, 2023 -
Commits on Feb 8, 2023
-
Merge pull request #2837 from cgarciae:improve-remat-docs
PiperOrigin-RevId: 508161859
Flax Authors committedFeb 8, 2023
Commits on Feb 7, 2023
-
Merge pull request #2816 from jheek:lazy-init
PiperOrigin-RevId: 507650305
Flax Authors committedFeb 7, 2023 -
Merge pull request #2811 from arcAman07:main
PiperOrigin-RevId: 507648060
Flax Authors committedFeb 7, 2023
Commits on Feb 3, 2023
-
Replace uses of deprecated JAX sharding APIs with their new names in …
…jax.sharding. This change updates: * {jax.experimental.maps.Mesh, jax.interpreters.pxla.Mesh} to jax.sharding.Mesh * {jax.experimental.PartitionSpec, jax.experimental.pjit.PartitionSpec, jax.interpreters.pxla.PartitionSpec, jax.pxla.PartitionSpec} to jax.sharding.PartitionSpec * jax.experimental.maps.NamedSharding to jax.sharding.NamedSharding. PiperOrigin-RevId: 506995236 -
-
Merge pull request #2815 from chiamp:initializers_refactor
PiperOrigin-RevId: 506842072
Flax Authors committedFeb 3, 2023 -
Merge pull request #2827 from google:update-jax-dep
PiperOrigin-RevId: 506767322
Flax Authors committedFeb 3, 2023
Commits on Feb 2, 2023
-
Merge pull request #2843 from IvyZX:meta
PiperOrigin-RevId: 506736298
Flax Authors committedFeb 2, 2023 -
Make a separate Python module for Orbax-related utils.
PiperOrigin-RevId: 506731539
-
Replace uses of deprecated JAX sharding APIs with their new names in …
…jax.sharding. This change updates: * {jax.experimental.maps.Mesh, jax.interpreters.pxla.Mesh} to jax.sharding.Mesh * {jax.experimental.PartitionSpec, jax.experimental.pjit.PartitionSpec, jax.interpreters.pxla.PartitionSpec, jax.pxla.PartitionSpec} to jax.sharding.PartitionSpec * jax.experimental.maps.NamedSharding to jax.sharding.NamedSharding. PiperOrigin-RevId: 506722866 -
-
Apply suggestions from code review
Co-authored-by: Marc van Zee <marcvanzee@gmail.com>
-
Merge pull request #2830 from chiamp:import_initializers
PiperOrigin-RevId: 506669714
Flax Authors committedFeb 2, 2023 -
Bumps minimal JAX version from 0.3.16 to 0.3.24 and cleans up some code.
Uses jax.local_devices() as argument to jax.device_put_replicated and jax.device_put_sharded, removing the custom logic for older JAX versions. PiperOrigin-RevId: 506667707
-
Clarify we are using the ReZero trick in our ResNet example.
PiperOrigin-RevId: 506666617
-
Bumps minimal JAX version from 0.3.16 to 0.3.24 and cleans up some code.
Uses jax.local_devices() as argument to jax.device_put_replicated and jax.device_put_sharded, removing the custom logic for older JAX versions. PiperOrigin-RevId: 506573580
-
Apply suggestions from code review
Co-authored-by: Marc van Zee <marcvanzee@gmail.com>
-
Merge pull request #2833 from levskaya:relaxed_naming
PiperOrigin-RevId: 506463179
Flax Authors committedFeb 2, 2023 -
Introduce relaxed naming policy behind a feature flag.
Historically Flax had strong opinions about how variables and submodules could be named, in the spirit of maintaining a single coherent namespace amongst python attributes, variable, and submodule names. It turns out we never really enforced that "single namespace" concept correctly, and furthermore, that the motivations for such a thing were very weak at best and any possible advantages left unrealized. In practice, these name constraints are just really annoying to our users and mostly just get in the way, especially with advanced configuration systems. This PR removes the pointless constraints: - "Adopted" modules brought in from the outside, as commonly occurs with configuration systems like fiddle, gin, etc. are now able to carry "scope names" which are not reset on adoption during module construction. - Variables in different collections in the same scope/module can have the same "scope name" in the variable nested dict. Conflicts between submodule names and variable names are still enforced. - We no longer force variable "scope names" not to clash with python attributes on the module. We only enforce non-collision within the backing scope itself. Since some of these changes could potentially change checkpoints in certain situations, this new behavior is released behind a flag "flax_relaxed_naming" for the time being.
Commits on Feb 1, 2023
-
Merge pull request #2831 from cgarciae:improve-map_variables-v2
PiperOrigin-RevId: 506321289
Flax Authors committedFeb 1, 2023 -
Merge pull request #2769 from cgarciae:fix-tabuluate-non-array-values
PiperOrigin-RevId: 506321251
Flax Authors committedFeb 1, 2023 -
-
Commits on Jan 31, 2023
-
-
Merge pull request #2818 from cgarciae:improve-map-variables-docs
PiperOrigin-RevId: 506136633
Flax Authors committedJan 31, 2023 -
Merge pull request #2819 from cgarciae:cache-mypy
PiperOrigin-RevId: 506121453
Flax Authors committedJan 31, 2023 -
-

